CVE-2025-22336
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in Amos Lee（一刀） Wizhi Multi Filters by Wenprise wizhi-multi-filters allows Stored XSS.This issue affects Wizhi Multi Filters by Wenprise: from n/a through <= 1.8.6.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCross-Site Request Forgery (CSRF) vulnerability in the Wizhi Multi Filters WordPress plugin allows attackers to trick authenticated users into submitting malicious requests that result in Stored XSS. The plugin lacks proper CSRF protection (nonce tokens) on state-changing forms, enabling attackers to inject persistent malicious scripts that execute when other users view affected pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed plugin versionNavigate to WordPress admin > Plugins > Installed Plugins > locate Wizhi Multi Filters and read the version number displayedAffected if version is unpatched or unknown (no fixed version provided, so any version lacking CSRF nonce implementation is affected)
-
Inspect plugin PHP files for nonce verificationAccess plugin files via FTP or File Manager, locate PHP files containing form handlers (typically files with form processing, AJAX handlers, or settings pages), search for presence of 'wp_nonce_field', 'wp_nonce_url', 'check_admin_referer', or 'check_ajax_referer' functionsAffected if forms that handle state-changing operations lack nonce verification code
-
Check form output for nonce fieldsView page source of any plugin-generated form (filter settings, widget forms, admin pages), inspect HTML for hidden nonce input fields with names like '_wpnonce' or '_wp_http_referer'Affected if plugin forms missing these hidden nonce fields
-
Verify data sanitization on storageExamine plugin PHP source code where user-submitted data is saved to database (insert/update operations), look for sanitization functions like 'sanitize_text_field', 'esc_attr', 'esc_html' before database operationsAffected if user input is stored without proper sanitization functions
The environment is affected if the Wizhi Multi Filters plugin is installed and its forms lack CSRF nonce tokens while storing user input without sanitization, enabling stored XSS via CSRF.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement anti-CSRF nonces on all plugin forms and AJAX actions, and ensure all user-supplied data is properly sanitized before storage and escaped during output to prevent XSS.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22336 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22336 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data