CVE-2025-31400
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 icyleaf WS Audio Player ws-audio-player allows Stored XSS.This issue affects WS Audio Player: from n/a through <= 1.1.8.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability in the WS Audio Player plugin (versions up to 1.1.8) allows remote attackers to inject malicious JavaScript code that gets stored on the server (Stored XSS). This occurs because the application does not properly validate the origin of requests, enabling attackers to craft malicious requests that execute in authenticated users' 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.
-
Locate WS Audio Player pluginCheck your CMS plugin directory or administration panel for WS Audio Player. Note the exact version number displayed in the plugin metadata.Affected if The plugin is installed and version displays as 1.1.8 or lower
-
Verify version against affected rangeCompare your installed version to the affected range: all versions up to and including 1.1.8. Check the plugin changelog or version file if the admin panel does not show the full version number.Affected if Installed version is 1.1.8 or any earlier version (1.0.x, 1.1.x, etc.)
-
Confirm plugin is activeInspect your site to determine if the WS Audio Player is actively loaded and rendering audio players on pages. Check for audio player shortcodes, widgets, or frontend output.Affected if The plugin is enabled and processing requests on your website
-
Inspect for CSRF protectionExamine the plugin source code for state-changing operations (settings forms, audio uploads, playlist modifications). Look for nonce verification, CSRF tokens, or referer/origin header validation in the code.Affected if No CSRF token validation or origin checking is implemented for the plugin's functionality
You are affected if WS Audio Player plugin version 1.1.8 or lower is installed and active, with no CSRF protection on its state-changing operations.
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 dataUpdate WS Audio Player to the latest patched version once available. Until then, implement CSRF tokens/validators for all state-changing operations and ensure proper input sanitization on the server side.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31400 — 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-31400 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