CVE-2025-58687
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 WP CMS Ninja Current Age Plugin current-age allows Stored XSS.This issue affects Current Age Plugin: from n/a through <= 1.6.
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 WordPress 'Current Age' plugin (versions up to 1.6) allows authenticated administrators to be tricked into performing unintended actions that inject malicious JavaScript (Stored XSS). An attacker can craft a malicious link that, when clicked by an authenticated admin, causes the admin's browser to send a request that stores XSS payload in the plugin settings.
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 Current Age plugin is installedGo to WordPress admin dashboard > Plugins and check if 'Current Age' plugin appears in the installed plugins listAffected if Plugin is installed and active in WordPress
-
Check installed plugin versionIn Plugins list, find 'Current Age' and locate the version number displayed under the plugin name. Compare this to version 1.6Affected if Version is 1.6 or lower (any version up to and including 1.6)
-
Inspect plugin settings for injected scriptsNavigate to the plugin settings page (usually under Settings > Current Age or a dedicated menu item). View the page source or inspect form fields for any script tags, event handlers (onclick, onload, etc.), or encoded JavaScript in text inputsAffected if Any script tags, javascript: URIs, or suspicious event handlers found in stored settings
-
Review WordPress activity logs for admin actionsCheck WordPress audit logs, server access logs, or security plugins for POST requests to admin-ajax.php or settings pages related to Current Age plugin that occurred without proper nonce verificationAffected if Requests to plugin endpoints found lacking nonce token validation
-
Check browser console for stored XSSAs an authenticated administrator, visit the Current Age plugin settings page and open browser developer console. Look for any console errors or executed scripts that were not intentionally addedAffected if Unexpected JavaScript executes or console shows script injection errors on plugin settings page
User is affected if Current Age plugin versions up to 1.6 are installed, an administrator visits the plugin settings after clicking a malicious link, and XSS payload is present in stored plugin settings.
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 the latest version when available. Until then, disable the plugin or implement WordPress nonce verification on all form actions and admin AJAX endpoints, and ensure all stored data is properly sanitized before output.
- 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-58687 — 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-58687 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