CVE-2025-23702
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 Schalk Burger Anonymize Links anonymize-links allows Stored XSS.This issue affects Anonymize Links: from n/a through <= 1.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 · high confidenceThis is a CSRF (Cross-Site Request Forgery) vulnerability in the WordPress plugin 'Anonymize Links' (versions <= 1.1) that allows attackers to inject Stored XSS payloads. The lack of anti-CSRF tokens on admin actions enables authenticated administrators to be tricked into unknowingly submitting malicious requests that store XSS payloads in the database, which then executes when other users view the affected links.
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 if Anonymize Links plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Anonymize Links', or check the /wp-content/plugins/ directory for the anonymize-links folderAffected if The plugin is present in the WordPress installation
-
Determine the installed plugin versionIn WordPress admin Plugins page, click on the plugin name 'Anonymize Links' to view the version number in the plugin details, or read the version header from the main plugin PHP fileAffected if The version is 1.1 or lower
-
Identify admin pages that handle link anonymizationAccess the plugin admin menu (typically under Settings or Tools) where users configure anonymized links. These are the endpoints that lack CSRF protection.Affected if The plugin provides admin interfaces for managing anonymized links where admin actions can be performed
-
Check for stored XSS in the link databaseQuery the WordPress database (wp_options table or custom table created by the plugin) for any anonymized link entries that contain suspicious script tags, iframe tags, or event handlers like onload/onerrorAffected if The database contains any link entries with unencoded JavaScript or HTML content that could execute in a user's browser
A WordPress site is affected if the Anonymize Links plugin is installed at version 1.1 or lower, and either the plugin lacks nonce verification on admin actions or malicious link entries with XSS payloads exist in the database.
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 (nonces) for all state-changing admin actions and apply proper input sanitization with output encoding to prevent XSS injection.
- 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-23702 — 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-23702 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