CVE-2026-10083: APCu Manager WordPress Plugin Stored XSS Vulnerability
The APCu Manager WordPress plugin versions before 4.5.0 contain a stored cross-site scripting (XSS) vulnerability in the admin dashboard. An attacker can inject malicious JavaScript into cache keys that persist in the object cache. When an administrator visits the plugin's admin page, the unescaped cache keys execute JavaScript in their browser session, potentially compromising the administrator's account or WordPress installation.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
- Weaknesses (CWE)
- —
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-29 / 2026-06-29
NVD description (verbatim)
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.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
The vulnerability exists because APCu Manager fails to escape APCu object-cache keys before rendering them on admin-area pages. Cache keys can be populated from unsanitized user input—for example, transient names created through unauthenticated requests to the plugin—and these keys are output directly to HTML without escaping. Because the cache persists across requests, the payload remains in the object cache until manually flushed, making this a stored XSS rather than a reflected variant. The attack requires that persistent object caching be enabled and that an admin view the affected page after malicious cache keys have been set.
Business impact
Administrator accounts are the primary target, and compromise at that level can lead to installation-wide damage: modification of site content, installation of malicious plugins, user account creation, or data exfiltration. The stored nature of the vulnerability means the attack persists invisibly until the cache is flushed, and every administrator who views the affected page during that window becomes a potential victim. WordPress sites relying on APCu for performance optimization are disproportionately at risk.
Affected systems
WordPress installations using the APCu Manager plugin version 4.4.9 or earlier. The vulnerability only manifests when persistent object caching is enabled. Sites using external cache backends or no persistent caching are not affected. The plugin is actively maintained; version 4.5.0 and later contain the fix.
Exploitability
Exploitation requires an attacker to inject malicious input into a cache key—typically through an unauthenticated request that creates a transient or similar cache entry. No special privileges are needed to poison the cache. However, the attack does depend on an administrator visiting the plugin's admin page after the cache has been polluted, and the payload must survive until that visit. Network accessibility is required, and the attack succeeds only if object caching is enabled. The CVSS score of 7.5 (HIGH) reflects high confidentiality and integrity impact but the additional constraint that user interaction (admin page view) is required.
Remediation
Update APCu Manager to version 4.5.0 or later immediately. This version includes proper escaping of cache keys in admin output. Verify the update is applied by checking the plugin version in WordPress admin or via the plugin file header. As an interim measure pending patching, disable persistent object caching or restrict admin page access via firewall or authentication rules if feasible, though these are not substitutes for patching.
Patch guidance
Patch version 4.5.0 or later is required. Administrators should navigate to Plugins > Installed Plugins in WordPress admin, locate APCu Manager, and click 'Update' if available. Alternatively, update via command line or WordPress administrative REST API if automation is in place. After updating, verify the new version is active and consider flushing the object cache to clear any potentially malicious keys that may have accumulated. Test admin pages to ensure no JavaScript errors occur post-update.
Detection guidance
Monitor object-cache contents for anomalous transient or cache-key names containing JavaScript payloads, HTML tags, or encoded special characters. Web application firewalls (WAF) can detect and block requests attempting to inject such keys if a parameter-injection pattern is known. Review admin access logs for unusual patterns of admin page visits by the same IP or user immediately after request bursts to transient-creation endpoints. APCu Manager itself may log admin page access; correlate timestamps between cache operations and admin page views to identify attack sequences.
Why prioritize this
Stored XSS targeting administrators justifies immediate patching due to the high-privilege nature of WordPress admin accounts. The attack requires no special permissions to trigger and affects any site with APCu caching enabled. Although the vulnerability is not yet on the KEV catalog, the attack surface is broad and the damage potential is severe. Prioritize this among WordPress plugin updates.
Risk score, explained
The CVSS 7.5 HIGH score reflects the combination of high confidentiality and integrity impact (C:H, I:H, A:H) against admin context, moderated by the attack vector requiring network access but with some network complexity (AC:H) and mandatory user interaction (UI:R). The lack of privilege escalation requirement (PR:N) and limited scope (S:U) yield the score. For organizations running APCu caching, the practical risk is elevated because exploitation is feasible with minimal attacker sophistication.
Frequently asked questions
Do I need to flush the cache after updating to 4.5.0?
While not strictly required for security, flushing the object cache after updating removes any malicious cache keys that may have accumulated before the patch was applied. Use the 'Flush Cache' option in APCu Manager admin settings or equivalent command-line tools.
What if I'm not using persistent object caching?
If your WordPress site does not use persistent object caching (e.g., APCu, Redis, Memcached), you are not affected by this vulnerability. The attack requires cache persistence across requests. However, you should still update APCu Manager to the patched version to prevent issues if caching is enabled in the future.
Can this vulnerability be exploited if I restrict admin access by IP?
IP restrictions reduce exposure but do not eliminate the vulnerability. An attacker only needs to inject cache keys (which can be done from any IP in an unauthenticated manner); they do not need admin access themselves. However, IP-restricting admin pages does prevent the attack from executing in admin sessions if the attacker cannot reach that page, so it provides defense-in-depth.
Is this vulnerability in the CISA KEV catalog?
No, this vulnerability is not currently tracked in CISA's Known Exploited Vulnerabilities catalog. However, the high CVSS score and ease of exploitation should prompt prompt patching regardless of KEV status.
This analysis is based on the CVE description and publicly available vendor information current as of the publication date. Security researchers and administrators should verify patch availability and applicability against their specific WordPress and plugin deployment before applying updates. SEC.co does not guarantee the accuracy of vendor patch notes or the completeness of affected product listings; consult official vendor advisories for authoritative guidance. The information provided is for informational purposes and should not be construed as legal or professional security advice. Source: NVD (public-domain), retrieved 2026-08-07. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2016-20062HIGHSQL Injection in Simply Poll 1.4.1 WordPress Plugin - Unauthenticated Data Theft
- CVE-2016-20063HIGHSQL Injection in Single Personal Message 1.0.3 – Credential & Data Theft Risk
- CVE-2016-20065HIGHUnauthenticated SQL Injection in Product Catalog 8 WordPress Plugin
- CVE-2016-20066HIGHWordPress CP Polls 1.0.8 Persistent XSS Vulnerability
- CVE-2016-20068HIGHUnauthenticated SQL Injection in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2016-20069HIGHUnauthenticated SQL Injection in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2016-20071HIGHCritical SQL Injection in WordPress 404 Redirection Manager Plugin v1.0
- CVE-2016-20072HIGHBBS e-Franchise WordPress Plugin SQL Injection – Remote Data Exfiltration Risk