CVE-2025-23961
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 · uneditedMissing Authorization vulnerability in wptasker WordPress Graphs & Charts graph-lite allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WordPress Graphs & Charts: from n/a through <= 2.0.8.
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 confidenceMissing authorization vulnerability in the WordPress Graphs & Charts plugin (graph-lite component) allows unauthorized access due to incorrectly configured access control security levels, potentially enabling unauthenticated users to view or modify chart data they should not have permission to access.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 WordPress Graphs & Charts plugin is installedNavigate to WordPress admin Dashboard > Plugins and look for 'Graphs & Charts' or 'WordPress Charts and Graphs' in the installed plugins listAffected if Plugin is installed and active
-
Identify the installed plugin versionIn Plugins list, click on the plugin name to view details, or check the plugin main PHP file for the 'Version' header comment in the plugin commentsAffected if Version matches or falls within the affected range (if any specific versions are known)
-
Confirm graph-lite component is in useCheck if chart shortcodes or widgets from the plugin are being used on the site by searching for '[graph-lite' or similar shortcodes in posts/pages, or check plugin settings/pages that reference graph-liteAffected if graph-lite component is actively used on the site
-
Test unauthorized access to AJAX endpointsUse a browser tool or curl to send a request to the plugin's AJAX endpoints (typically /wp-admin/admin-ajax.php?action=graph_lite_*) without authentication or valid nonce, observe if data is returned without authorization checkAffected if AJAX endpoints return chart data or allow modifications without requiring authentication or capability verification
-
Inspect access control on sensitive functionsExamine the plugin's PHP source code, specifically the graph-lite component files, for presence of WordPress capability checks (like current_user_can, check_ajax_referer, wp_verify_nonce) on functions handling chart dataAffected if No capability checks or nonce verification found in functions processing chart data requests
If the WordPress Graphs & Charts plugin with graph-lite component is active and AJAX endpoints or sensitive functions lack proper authorization checks, the site is affected by this vulnerability.
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 proper WordPress capability and nonce checks on all sensitive functions and AJAX endpoints within the graph-lite component to enforce role-based access control.
- 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-23961 — 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-23961 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