Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLocate Multisite subdirectory site with open registration
-
ExploitWait for genuine registrant to follow activation link
-
ExecutionRequest publicly cached wp-activate.php file
-
ImpactExtract plaintext username and twelve-character password
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V3 - Web Frontend Security Cache-Control for sensitive pages
|
| Exploitation Conditions | Exploitation is strictly gated: the site must be a WordPress Multisite SUBDIRECTORY installation with public user AND site registration enabled, and WP Fastest Cache (<=1.5.3) must be caching the wp-activate.php response despite its no-store/no-cache headers, the wp-activate-* cookie, and the WP_INSTALLING state. Credentials are exposed ONLY after a genuine registrant actually follows their activation link, and only the MOST RECENTLY activated registrant's username and twelve-character password are present in the cached file, making the exposure window transient and dependent on real registration activity the attacker does not control. These conditions - non-default Multisite mode, open registration, and reliance on a legitimate user's activation event - are the primary limiting factors and explain the AC:H rating. |
| Impact | Signals point to a genuine but conditional, moderate-severity issue rather than a top-priority emergency. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N, base 5.9 MEDIUM) shows network reach with no authentication, but the high attack complexity reflects real preconditions outside the attacker's control. The vuln.today decision label is 'this_month' (not act_now/emergency), it is not on CISA KEV (no confirmed active exploitation), and no EPSS score was supplied in the input, so widespread-exploitation probability cannot be quantified here. There is no public exploit identified at time of analysis - the references contain only the Wordfence advisory, WordPress trac source lines, and the fixing changeset (3749897), none of which is a PoC. The confidentiality impact is real and serious (plaintext credential disclosure, C:H), but exploitation hinges on a narrow configuration (Multisite subdirectory with open registration) and on a legitimate registrant actually completing activation, with only the most-recently-activated account exposed in a transient cache window. Net: treat as a real but scoped priority - patch within the vendor/priority 'this_month' window; it is not a mass, default-configuration internet threat. |
| Exploit ScenarioDerived | An attacker monitors a WordPress Multisite subdirectory installation that runs WP Fastest Cache and allows public user/site registration. After a genuine new registrant follows their activation link, the plugin caches the wp-activate.php response to a publicly readable file; the attacker then requests that cached file and reads the registrant's plaintext username and twelve-character password. No public exploit code was identified at time of analysis, and the attack only works against the most recently activated account. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 03, 2026
WP Fastest Cache, a WordPress caching plugin, writes the full response of Core's wp-activate.php to a publicly readable cache file in versions up to and including 1.5.3, ignoring that endpoint's no-store/no-cache headers, its wp-activate-* cookie, and the WP_INSTALLING state. Because WordPress prints the new account's plaintext username and twelve-character password on that activation screen, unauthenticated attackers who can request the cached file can read the credentials of the most recently activated Multisite registrant. The exposure is heavily gated: the site must be a Multisite subdirectory installation with both public user and site registration enabled, and a real registrant must have just followed their activation link; the vulnerability is not known to be actively exploited (no CISA KEV entry) and no public exploit code was identified at time of analysis.
RemediationAI
Update WP Fastest Cache to a release built after changeset 3749897 (https://plugins.trac.wordpress.org/changeset/3749897/wp-fastest-cache), which is the upstream fix for the wp-activate.php caching behavior; the previously affected build is 1.5.3 and earlier, and a patched tagged release should be confirmed on the plugin's WordPress.org page before deployment. Because fixes to a page-cache plugin are configuration-sensitive, verify after upgrading that activation responses are no longer materialized in the cache directory. Where upgrading is not immediately possible, the practical compensating controls are to keep public user and site registration disabled on Multisite networks that do not need them (this removes the exposure entirely, at the cost of blocking self-service signups), or to exclude wp-activate.php from caching through the plugin's exclusion rules and purge the existing cache so any stored activation response is removed - noting that an overly broad exclusion list reduces the cache hit rate and that any cached copy already fetched must be treated as compromised credentials. Sites that ran an affected version with open Multisite registration should also consider the recently activated accounts' passwords exposed and force a reset.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a cache-poisoning-of-confidentiality class issue (CWE-524: use of a cache containing sensitive information) inside WP Fastest Cache's page-caching logic, which is implemented in inc/cache.php of the plugin (the advisory references lines 83, 452, 567, 1027 and 1400 of the 1.5.2 tag). WordPress's wp-activate.php is a Core endpoint that normally suppresses caching through no-store/no-cache response headers, a wp-activate-* cookie, and the WP_INSTALLING constant; a correct page cache must honor all three signals and refuse to store the response. WP Fastest Cache does not, in the affected versions, exclude wp-activate.php from caching, so the rendered activation confirmation - which by WordPress design includes the generated account name and password for the newly activated Multisite user - is serialized to a static HTML file under the plugin's public cache directory. Any unauthenticated visitor able to request that cache path then reads the stored credentials. Per the assessed vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N, CVSS 5.9), the attacker needs no credentials and no victim interaction directly, but the high attack-complexity component reflects real preconditions: the site must run WordPress Multisite in subdirectory mode with public user and site registration enabled, caching must be active for wp-activate.php, and a legitimate registrant must have followed their activation link before the attacker fetches the file. Only the most recently activated registrant's credentials are present, so the window is transient rather than a standing credential dump.
Know when PHP gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Cache file is network-retrievable with no auth (AV:N/PR:N); success depends on uncontrolled timing of a genuine registrant's activation plus non-default Multisite config (AC:H); full credential disclosure gives C:H with no integrity or availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The WP Fastest Cache plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.5.3. The plugin caches the response of Core’s wp-activate.php without honoring its no-store/no-cache headers, the wp-activate-* cookie, or the WP_INSTALLING state, writing the credential-bearing activation response to a publicly accessible cache file. This makes it possible for unauthenticated attackers to retrieve the plaintext username and twelve-character password of the most recently activated Multisite registrant from that cached wp-activate.php response. Exploitation requires a Multisite subdirectory installation with public user and site registration enabled, and the credentials are only exposed after a genuine registrant follows their activation link.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
EUVD-2026-115657
GHSA-8338-x748-jf52
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB