CVE-2025-32500
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 Sudavar Codescar Radio Widget codescar-radio-widget allows Stored XSS.This issue affects Codescar Radio Widget: from n/a through <= 0.4.2.
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 confidenceCSRF vulnerability in Codescar Radio Widget <=0.4.2 allows attackers to forge requests that inject malicious JavaScript (Stored XSS). An authenticated admin can be tricked into submitting a crafted request that stores the XSS payload, which then executes 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 version of Codescar Radio WidgetAccess the WordPress plugin directory or admin panel, locate Codescar Radio Widget in the plugins list, and note the installed version number from the plugin header or version fileAffected if the version displayed is 0.4.2 or lower
-
Confirm plugin is currently activeCheck the WordPress admin under Plugins > Installed Plugins to verify that Codescar Radio Widget is activatedAffected if the plugin shows as active and the version is in the affected range
-
Verify CSRF protection is absent from admin formsInspect the plugin source code for forms and AJAX handlers used by the widget, specifically looking for the presence of nonce verification or CSRF token validation on form submissionsAffected if admin forms and AJAX endpoints lack nonce or token verification logic
-
Scan for existing XSS payloads in stored widget dataQuery the WordPress database tables where plugin settings or widget content are stored (such as wp_options or wp_postmeta) for suspicious script tags or event handler attributes that may have been injectedAffected if any stored records contain JavaScript code or HTML that was not intentionally added by the site administrator
You are affected if Codescar Radio Widget is installed with version 0.4.2 or lower and the plugin lacks CSRF protection on its admin forms, or if malicious scripts are already present in stored widget data.
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 to the patched version of Codescar Radio Widget. If no patch exists, implement anti-CSRF tokens (nonces) on all forms and AJAX endpoints in the plugin.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32500 — 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-32500 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