CVE
WordPress Quality theme <= 3.3 - Cross Site Request Forgery (CSRF) vulnerability
WordPress Quality theme version 3.3 and earlier is affected. 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. Quality theme version 3.3 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
The webriti Quality WordPress theme has a cross-site request forgery flaw that lets a remote attacker, without logging in, make a logged-in user's browser carry out unwanted actions on the site if that user is tricked into opening a malicious web page. The attacker needs the user to take that action, such as clicking a link.
Read the original description
Cross-Site Request Forgery (CSRF) vulnerability in webriti Quality quality allows Cross Site Request Forgery.This issue affects Quality: from n/a through 3.3.
Who should check
Teams running the WordPress Quality theme (webriti Quality) version 3.3 or earlier
Read the source excerpt
“WordPress Quality Theme <= 3.3 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.
Quality theme version 3.3 or earlierWorkaround: The checked facts list no workaround. The only stated scope is the theme version range up to and including 3.3.
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-125838 (WordPress Quality theme <= 3.3 - 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-125838 (entry last updated 2026-11-11):
Affected:
- webriti Quality: through 3.3
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Quality theme version 3.3 or earlier (source: https://patchstack.com/database/wordpress/theme/quality/vulnerability/wordpress-quality-theme-3-3-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-125838 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125838 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/quality/vulnerability/wordpress-quality-theme-3-3-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-125838
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-125838"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- quality
through 3.3
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-125838
Is CVE-2026-125838 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?
Logged-in users can be tricked into performing actions they did not intend, such as changing passwords or making purchases, through forged cross-site requests (CSRF).Source: patchstack.com
Which versions are affected by CVE-2026-125838?
quality: through 3.3.Source: cve.now feed data
Am I affected, and how do I check?
The Quality theme by webriti, version 3.3 or earlier, is in the affected range. To check an installed copy, look at the theme version under Appearance > Themes in the WordPress admin.Source: patchstack.com
How do I fix CVE-2026-125838?
The checked facts do not name a fixed version, so no upgrade target can be stated. Check the vendor for a release newer than 3.3.Source: patchstack.com
What if there's no patch?
The checked facts list no workaround. The only stated scope is the theme version range up to and including 3.3.Source: patchstack.com