Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister or use subscriber account
-
DeliverySend crafted AJAX request to vulnerable action
-
ExploitBypass missing capability/nonce check
-
ExecutionReceive all users' names and emails
-
ImpactHarvest admin contacts for phishing
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated subscriber-level (or higher) account on a WordPress site running zportals before 6.4.2 (PR:L), which is trivially obtained where open user registration is enabled - the common default that removes any real barrier. The specific limiting factor is the absence of a capability check AND a nonce check on one particular AJAX action, so no admin privileges and no user interaction are needed; exploitation is remote over the network against default plugin behavior. Impact is bounded to confidentiality of user display names and email addresses only (no data modification or service disruption). |
| Impact | This is a genuine but modestly-scoped issue. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, base 4.3, MEDIUM) is internally consistent with the description: a network-reachable AJAX action, trivial to trigger, requiring only a low-privilege (subscriber) authenticated session, with confidentiality-only impact and no integrity or availability effect. No EPSS score, KEV listing, SSVC decision, or POC is present in the input, so there is no signal of active or automated exploitation - per the precision rule this is 'no public exploit identified at time of analysis.' The realistic risk is that of an authenticated information-disclosure/enumeration bug: on WordPress sites permitting open user registration (the common default that makes subscriber accounts freely obtainable), any registered user can harvest the display name and email of every account including administrators, which is valuable for targeted phishing/credential-stuffing but is not directly a compromise. This is a real-but-low-priority issue rather than a high-severity emergency; the 4.3 rating is not inflated. No key signals conflict; the main missing data are EPSS/KEV/POC status, which are simply absent (not an error). |
| Exploit ScenarioDerived | An attacker self-registers a free subscriber account on a WordPress site running zportals < 6.4.2 (or uses any low-privilege account they already hold), then sends the unprotected AJAX request that lacks capability and nonce checks. The response returns the display name and email address of every registered user, including administrators, which the attacker uses to build a targeted phishing or password-spray list. No public exploit is identified in the provided data, but the missing authorization/nonce check makes the request trivial to reproduce. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 23, 2026
Subscriber-level users of the WordPress zportals plugin before version 6.4.2 can harvest the display name and email address of every registered account, including administrators, by calling an AJAX action that performs neither a capability check nor a nonce check. The requirement for a low-privileged authenticated account (PR:L in the assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N vector) is the only real barrier, and it largely disappears on sites with open registration enabled; no user interaction is needed. Impact is confined to confidentiality of directory-style user data - no data modification or service disruption - and no public exploit code was identified at time of analysis, with the vendor having shipped a fix in 6.4.2.
RemediationAI
Apply the vendor-released patch by upgrading the zportals plugin to version 6.4.2 or later, which restores the missing capability and nonce checks on the AJAX action; the WPScan advisory at https://wpscan.com/vulnerability/752e218f-bd97-40d4-b32b-9e913b520db6/ and the NVD entry at https://nvd.nist.gov/vuln/detail/CVE-2026-18365 document the fix. Where immediate patching is not possible, the highest-value compensating control is to disable open user self-registration (Settings > General > Membership) and audit/remove existing subscriber accounts, since the attack presupposes a low-privileged login - the trade-off is that legitimate public sign-ups, membership sites, and comment-driven account creation stop working. Additional short-term measures include blocking or rate-limiting requests to the vulnerable admin-ajax.php action at the WAF or reverse-proxy layer and, in managed environments, restricting AJAX access to trusted roles; these are imperfect because the action name and parameters can be varied, and a WAF rule that is too broad may break legitimate plugin functionality. Because only display names and email addresses are exposed, prioritize this behind actively exploited issues, but treat leaked addresses as a phishing and credential-stuffing precursor and monitor for credential-stuffing attempts against the affected site, since the harvested data cannot be un-disclosed once retrieved.
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 vulnerability maps to CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) and is rooted in two missing authorization controls on a WordPress AJAX handler. WordPress plugins register AJAX entry points through the wp_ajax_{action} hook (authenticated) or wp_ajax_nopriv_{action} (unauthenticated); a hardened handler must both verify intent with a nonce (e.g., check_ajax_referer) and enforce authorization with a capability check (e.g., current_user_can('list_users') or similar). In zportals before 6.4.2 the affected action omits both, so any logged-in account - even the lowest-privileged subscriber role - can invoke the endpoint directly and receive the display names and email addresses of the full user table, which WordPress exposes through core functions such as get_users()/WP_User_Query. Because subscriber accounts are freely obtainable wherever self-registration is open, the effective attack surface is close to unauthenticated on those deployments, though the assessed vector correctly scores the prerequisite account as PR:L. The flaw is an access-control defect rather than an injection or memory-safety issue, so exploitation is deterministic and requires no special tooling beyond an HTTP client carrying a valid subscriber cookie.
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:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Network AJAX action with no complexity barrier but requiring a subscriber account (PR:L); discloses only names/emails so C:L, with no integrity or availability impact.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
4DescriptionCVE.org
The zportals WordPress plugin before 6.4.2 does not perform any capability or nonce check on one of its AJAX actions, allowing users with a subscriber-level account to disclose the display name and email address of every registered user, including administrators.
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-85023
GHSA-xr35-jw5p-9pmm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB