CVE-2025-32480
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 dalziel Windows Live Writer windows-live-writer allows Stored XSS.This issue affects Windows Live Writer: from n/a through <= 0.1.
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 the dalziel Windows Live Writer WordPress plugin allows attackers to craft malicious requests that result in stored XSS. The lack of anti-CSRF tokens on vulnerable forms enables attackers to inject malicious scripts that persist in the application.
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 dalziel Windows Live Writer plugin is installedAccess WordPress admin panel, navigate to Plugins section, and verify the dalziel Windows Live Writer plugin appears in the installed plugins listAffected if The plugin is present and active in the WordPress installation
-
Identify plugin versionIn the Plugins list, click on the plugin details link for dalziel Windows Live Writer and locate the version number displayed in the plugin metadataAffected if The installed version is older than any patched version released by the vendor (if a fix version becomes known, compare your version to it)
-
Inspect plugin forms for anti-CSRF tokensNavigate to any form rendered by the dalziel Windows Live Writer plugin (such as settings or submission forms), view the page source, and search for nonce fields or tokens with names like _wpnonce, csrf_token, or similar security tokensAffected if The plugin forms lack anti-CSRF token fields entirely or the tokens are missing from state-changing operations
-
Check for stored XSS in plugin-generated contentUse WordPress admin or database query to examine any data or content created by the plugin; inspect the HTML output of plugin pages using browser developer tools to see if unsanitized user input appears in page sourceAffected if User-supplied input is stored and rendered without proper escaping, resulting in executable script tags in page output
You are affected if the dalziel Windows Live Writer plugin is installed and its forms lack anti-CSRF token protection, allowing potential stored XSS injection.
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 state-changing forms and sanitize/escape all user-supplied input before storage and output to prevent stored XSS.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32480 — 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-32480 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