dbcve.org
VulnerabilityAwaiting classification

CVE-2026-10083

HIGH · 7.5 CVSS v3.1 Published 2026-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges 8 weeks old

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 · unedited
The APCu Manager WordPress plugin before 4.5.0 does not escape APCu object-cache keys before rendering them in an admin-area page, leading to a Stored Cross-Site Scripting vulnerability. When a persistent object cache is enabled, cache keys derived from unsanitised user input (e.g. a transient name created by another APCu Manager WordPress plugin before 4.5.0 from an unauthenticated request) are output without escaping and execute arbitrary JavaScript in the session of an administrator viewing the page.

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 confidence

The APCu Manager WordPress plugin before 4.5.0 fails to escape APCu object-cache keys before rendering them in admin-area pages, creating a Stored XSS vulnerability. When persistent object cache is enabled, cache keys derived from unsanitized user input (such as transient names created by another plugin from unauthenticated requests) are output without escaping, allowing arbitrary JavaScript execution in administrator sessions.

MitigationUpgrade APCu Manager to version 4.5.0 or later, which properly escapes APCu object-cache keys before rendering them in admin pages.

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify APCu Manager plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'APCu Manager' or check the plugins directory for apcu-manager.php
    Affected if APCu Manager plugin is not found or not activated
  2. Check installed version of APCu Manager
    View the plugin file header in wp-content/plugins/apcu-manager/apcu-manager.php or check the plugins page in WordPress admin for the version number
    Affected if The version is below 4.5.0 (e.g., 4.4.x or earlier)
  3. Confirm persistent object cache is enabled
    Check for the presence of wp-content/object-cache.php file or inspect the WordPress debug bar/cache information in the admin area
    Affected if APCu object caching is enabled and wp-content/object-cache.php exists
  4. Inspect APCu cache keys for unsanitized data
    In WordPress admin, navigate to the APCu Manager settings page and examine the displayed cache keys, particularly those related to transients
    Affected if Any cache keys contain raw user-supplied input (transient names, custom keys) that appear unescaped in the admin interface

You are affected if APCu Manager version is below 4.5.0 AND persistent APCu object caching is enabled, allowing unsanitized cache keys to be displayed in the admin area.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade APCu Manager to version 4.5.0 or later, which properly escapes APCu object-cache keys before rendering them in admin pages.

Recommended fix High confidence

APCu Manager 4.5.0 or later

  1. Backup your WordPress site database and files
  2. Update the APCu Manager plugin to version 4.5.0 or later through the WordPress admin dashboard (Plugins > APCu Manager > Update Now)
  3. Alternatively, update via WP-CLI: wp plugin update apcu-manager
  4. Verify the update was successful by checking the plugin version in the installed plugins list
  5. Clear any APCu cache if possible to remove any potentially malicious cached keys that may have been stored

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10083 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10083 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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