CVE-2025-25160
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 Mark Barnes Style Tweaker style-tweaker allows Stored XSS.This issue affects Style Tweaker: from n/a through <= 0.11.
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 Style Tweaker plugin allows attackers to inject malicious JavaScript through stored XSS by tricking authenticated administrators into submitting crafted requests. The lack of CSRF token validation on form submissions enables attackers to craft requests that the victim's browser will execute, persisting the XSS payload.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 0.11CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Verify Style Tweaker plugin installation and versionNavigate to WordPress Admin > Plugins and locate 'Style Tweaker' by Mark Barnes. Check the version number displayed. Alternatively, inspect the main plugin file (style-tweaker.php) and look for the 'Version' header comment.Affected if The installed version is 0.11 or lower (any version <= 0.11).
-
Confirm plugin is activeCheck if Style Tweaker appears in the list of active plugins in WordPress Admin > Plugins > Active Plugins.Affected if The plugin is active and the version is <= 0.11.
-
Inspect form submission handlers for CSRF protectionExamine the plugin's PHP files that handle form submissions (typically functions processing POST requests for style/settings changes). Look for WordPress nonce verification functions such as wp_verify_nonce, check_admin_referer, or wp_nonce_field.Affected if Form handling code lacks nonce verification or CSRF token validation - no wp_verify_nonce, check_admin_referer, or similar CSRF protection calls are found in the form processing logic.
-
Inspect stored value rendering for XSS protectionExamine the PHP code that outputs or echoes stored style values back to the admin interface or frontend. Look for output escaping functions such as esc_html, esc_attr, esc_js, or similar encoding functions when rendering stored values.Affected if Stored values are rendered without proper output encoding - the code directly outputs stored data without esc_html, esc_attr, or other escaping functions.
-
Review admin forms for nonce field generationInspect the HTML forms within the Style Tweaker admin pages. Look for hidden input fields containing WordPress nonces (typically named '_wpnonce' or '_wp_http_referer') generated by functions like wp_nonce_field.Affected if Admin forms do not include hidden nonce fields - no _wpnonce or similar CSRF token fields are present in the HTML forms.
You are affected if the Style Tweaker plugin version is 0.11 or lower AND the plugin is active AND the code lacks CSRF token validation in form handlers AND stored values are rendered without 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 on all form submissions in Style Tweaker and validate these tokens server-side before processing any settings or style changes. Additionally, apply output encoding when rendering stored values to prevent XSS execution.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-25160 — 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-25160 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