CVE-2025-22343
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 koter84 wpSOL wpsol allows Stored XSS.This issue affects wpSOL: from n/a through <= 1.2.0.
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the wpSOL WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions that result in Stored XSS. The lack of anti-CSRF tokens enables malicious requests to be forged, and insufficient input sanitization allows JavaScript code to be persistently stored and executed in victims' browsers.
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.
-
Confirm wpSOL plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and search for wpSOL, or inspect the /wp-content/plugins/ directory for a wpSOL folderAffected if wpSOL plugin is not installed or not active
-
Identify wpSOL versionCheck the plugin header in wp-content/plugins/wpsol/main.php for 'Version:' value, or view the plugin details in WordPress plugin repositoryAffected if Version is unknown or older than the patched release (compare when available)
-
Inspect plugin for CSRF token implementationSearch plugin PHP files for nonce verification: look for 'wp_nonce_field', 'check_admin_referer', or 'verify_nonce' functions in files handling state-changing actions (forms, AJAX endpoints)Affected if State-changing operations lack nonce verification calls
-
Check input sanitization in plugin codeSearch PHP files for input handling (like $_POST, $_GET) and inspect whether sanitization functions are used (like sanitize_text_field, esc_html, esc_attr) before storing dataAffected if User-supplied data is stored without sanitization functions
-
Verify output encoding before displaying stored dataSearch for database retrieval operations and check if output uses encoding functions (like esc_html, esc_attr, esc_js) before rendering in HTML contextAffected if Stored data is echoed without proper output encoding
User is affected if wpSOL plugin is installed and state-changing operations lack CSRF nonce verification AND user input is stored/displayed without sanitization and output encoding.
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 tokens (nonces) for all state-changing operations and apply proper input sanitization and output encoding to prevent stored XSS. Users should update to a patched version when available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22343 — 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-22343 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