CVE-2025-32476
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 blueinstyle Advanced Tag Lists advanced-tag-list allows Stored XSS.This issue affects Advanced Tag Lists: from n/a through <= 1.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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Advanced Tag Lists plugin allows unauthenticated or low-privileged attackers to trick authenticated administrators into executing malicious requests that inject persistent JavaScript payloads into tag list entries, resulting in Stored XSS that executes when other users view the affected tag lists.
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.
-
Verify Advanced Tag Lists plugin is installedNavigate to your plugin management interface (typically /wp-admin/plugins.php in WordPress) or list installed plugins via database query on wp_options table looking for 'advanced-tag-lists' or similar plugin identifierAffected if Plugin named Advanced Tag Lists appears in the installed plugins list
-
Determine installed plugin versionAccess plugin details page in WordPress admin, or inspect plugin main file header for 'Version:' comment, or query the database wp_options table for the option_name containing plugin versionAffected if Version number is lower than the latest patched version (the vulnerability exists in versions lacking CSRF token validation and input sanitization)
-
Inspect tag list entries for injected contentNavigate to the Advanced Tag Lists admin interface and review all tag list entries. Alternatively, query the database table storing tag list entries, examining the fields that contain tag label/name values for unexpected script tags, HTML tags, or encoded payloadsAffected if Any tag list entry contains script tags, javascript: URLs, onload/onerror attributes, or other XSS vectors in the name/label fields
-
Review admin action logs for CSRF patternsCheck admin audit logs, activity logs, or server access logs for POST requests to tag list creation/modification endpoints originating from unexpected referrers or containing unusual parameter patterns that could indicate forced admin actionsAffected if Log entries show tag modifications from authenticated admin sessions with missing or invalid CSRF tokens
A user is affected if the Advanced Tag Lists plugin is installed and the installed version predates the CSRF token validation and sanitization fix, or if tag list entries already contain injected XSS payloads.
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 latest version of Advanced Tag Lists which includes CSRF token validation and proper input sanitization; implement SameSite cookie attributes as an additional defense-in-depth measure.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32476 — 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-32476 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