CVE
WordPress vice theme <= 1.4 - Cross Site Request Forgery (CSRF) vulnerability
Affects the webriti vice WordPress theme, version 1.4 and earlier. No vendor severity rating is given, and no fixed version is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. WordPress vice theme version 1.4 or earlier
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 27/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A cross-site request forgery flaw in the vice WordPress theme by webriti lets an attacker make a user unknowingly perform actions on the site. The attack can be launched remotely over the network without logging in, but it requires the victim to take an action.
Read the original description
Cross-Site Request Forgery (CSRF) vulnerability in webriti vice vice allows Cross Site Request Forgery.This issue affects vice: from n/a through 1.4.
Who should check
Sites running the webriti vice WordPress theme, version 1.4 or earlier
Read the source excerpt
“WordPress vice Theme <= 1.4 is vulnerable to Cross Site Request Forgery (CSRF)”
cve.now Index
- Exploitation0/40No signal
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 8.8, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
WordPress vice theme version 1.4 or earlierWorkaround: The checked facts list no fix and no workaround. Until one is published, consider whether the vice theme needs to stay active on the site.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-125844 (WordPress vice theme <= 1.4 - Cross Site Request Forgery (CSRF) vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-125844 (entry last updated 2026-11-11):
Affected:
- webriti vice: through 1.4
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- WordPress vice theme version 1.4 or earlier (source: https://patchstack.com/database/wordpress/theme/vice/vulnerability/wordpress-vice-theme-1-4-cross-site-request-forgery-csrf-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-125844 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125844 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/theme/vice/vulnerability/wordpress-vice-theme-1-4-cross-site-request-forgery-csrf-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-125844
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125844"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- vice
through 1.4
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125844
Is CVE-2026-125844 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
This is a cross-site request forgery flaw, which lets an attacker trick a logged-in user into performing actions they did not intend, such as changing passwords or making purchases.Source: patchstack.com
Which versions are affected by CVE-2026-125844?
vice: through 1.4.Source: cve.now feed data
Am I affected, and how do I check?
The vice theme by webriti, in version 1.4 and all earlier versions listed in the checked facts. To check a site's theme version, look at the theme's version in the WordPress Appearance > Themes screen.Source: patchstack.com
How do I fix CVE-2026-125844?
The checked facts name no fixed version, so no upgrade target can be given. Check the vendor's channels for an updated release.Source: patchstack.com
What if there's no patch?
The checked facts list no fix and no workaround. Until one is published, consider whether the vice theme needs to stay active on the site.Source: patchstack.com