CVE-2025-25135
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 Victor Barkalov Custom Links On Admin Dashboard Toolbar customize-wpadmin allows Stored XSS.This issue affects Custom Links On Admin Dashboard Toolbar: from n/a through <= 3.3.
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 Custom Links On Admin Dashboard Toolbar plugin allows authenticated attackers to inject malicious scripts via forged requests, leading to stored XSS. Attackers can trick administrators into submitting requests that store malicious links containing JavaScript payloads on the admin dashboard.
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 the plugin is installedLog into WordPress admin and go to Plugins > Installed Plugins, or check the wp-content/plugins directory for a folder named 'custom-links-admin-toolbar' or similarAffected if plugin named Custom Links On Admin Dashboard Toolbar or Custom Links On Admin Toolbar is present and active
-
Check the installed versionView the plugin on the Plugins page to see the version number, or open the main plugin PHP file and look for the Version header in the plugin comment blockAffected if version is 3.3 or lower
-
Check for existing custom linksNavigate to the plugin settings where custom toolbar links are configured (typically under Dashboard or a dedicated settings page), and inspect the stored link URLs and labels for suspicious JavaScript:// or script tagsAffected if any stored links contain javascript: URIs, <script> tags, or other unexpected script content
-
Inspect the plugin source codeOpen the main plugin PHP file and search for form handling functions, looking for whether $_POST or $_GET parameters are processed without nonce verification or proper sanitization (esc_url, esc_attr, sanitize_text_field)Affected if form submissions lack WordPress nonce checks and input is not sanitized before being stored or displayed
You are affected if the plugin is installed with version 3.3 or lower and lacks CSRF nonce validation and proper input sanitization in its form handling code, or if malicious links already exist in the toolbar configuration.
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 the plugin to a version beyond 3.3 that includes CSRF token validation and proper input sanitization. If no update is available, implement WordPress nonces for form submissions and use sanitization functions like esc_url() and esc_attr() on user-supplied link parameters.
- 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-25135 — 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-25135 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