EUVD-2026-89624
GHSA-59gj-2qfc-4w2p
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running vulnerable YayReviews
-
DeliveryLocate unauthenticated review API route
-
ExploitEnumerate review record IDs
-
ExecutionHarvest emails and pending review content
-
ImpactAggregate PII for abuse
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 | Exploitation requires only that the target WordPress site runs YayReviews between version 1.0.4 and before 1.4.1 with the vulnerable API route reachable; the route does not restrict access, so no authentication, user interaction, or special configuration is needed (PR:N/UI:N) for remote unauthenticated attackers to retrieve individual review records including pending-moderation reviews and reviewer email addresses. The main limiting factors are the plugin's modest deployment footprint and that impact is confined to disclosure of review-related PII (no write access or server compromise); patching to 1.4.1 removes the exposure. |
| Impact | This is a genuine but low-to-moderate priority issue rather than a critical one. The CVSS 3.1 base score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) accurately reflects an unauthenticated, network-reachable, low-complexity flaw whose only impact is limited confidentiality - leakage of reviewer email addresses and non-public/pending review content, with no integrity or availability impact. The SSVC decision framework reinforces a measured priority: Exploitation is 'none' (no observed active exploitation), Technical Impact is 'partial' (consistent with C:L only), but Automatable is 'yes' - meaning an attacker can trivially script bulk harvesting across many sites, raising the data-scraping/privacy risk even though per-request impact is small. No EPSS score, KEV listing, or public POC was provided in the input, so there is currently no evidence of weaponization. The signals are internally consistent (no conflicts between CVSS network vector and the description, which also describes an unauthenticated API route). The realistic risk is privacy/data-exposure and GDPR-relevant PII harvesting at scale rather than server compromise. |
| Exploit ScenarioDerived | An unauthenticated attacker discovers the plugin's REST/API route that returns individual customer review records and iterates over record identifiers to enumerate and download reviews, including those still pending moderation. Because the endpoint requires no authentication and the attack is automatable, the attacker scripts bulk collection of reviewers' email addresses and other non-public content across one or many WordPress sites running vulnerable YayReviews versions. No public exploit code was identified in the provided data at the time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Unauthenticated information disclosure in the YayReviews WordPress plugin (all releases before 1.4.1, with the EUVD entry listing 1.0.4 as the earliest confirmed affected version) allows remote attackers to retrieve individual customer review records from an API route that enforces no access control, including reviews still awaiting moderation. Per the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, no authentication, user interaction, or non-default configuration is required - the only prerequisite is that the site runs a vulnerable version with the route reachable - and the consequence is bulk harvesting of reviewers' email addresses and other non-public review content, with no integrity or availability impact. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the CISA SSVC assessment records Exploitation: none while flagging the issue as Automatable: yes, so the realistic risk is low-to-moderate PII exposure proportional to the plugin's modest deployment footprint rather than site compromise.
RemediationAI
Vendor-released patch: upgrade YayReviews to version 1.4.1 or later, which removes the unauthenticated exposure of individual review records and the pending-moderation content they contain; this is the primary and only complete fix, and it eliminates the issue with no further configuration. Until the upgrade can be staged, the most effective compensating control is to deny anonymous access to the plugin's review API route at the edge - block the corresponding /wp-json/ path (or the plugin's REST namespace) in a WAF, reverse proxy, or web server rule; the trade-off is that legitimate front-end review retrieval relying on that same route may break for visitors until the rule is scoped narrowly to the single-record endpoint. Deactivating the plugin entirely is a safe stopgap if review functionality is not business-critical, at the cost of losing existing review display. Restricting the endpoint by required authentication or IP allow-listing is weaker here, since the route is designed for anonymous front-end consumption and any authenticated client could still enumerate records. Monitoring web logs for sequential or automated requests to the review endpoint can detect harvesting attempts but does not prevent data loss, and because the flaw is marked Automatable: yes, exploitation is scriptable at scale, so patching should not be deferred on the assumption that low deployment numbers are protective. Confirm the fixed version against the vendor/WPScan advisory at https://wpscan.com/vulnerability/23965307-678d-4f59-beae-5a8b33af9a75/ and the NVD record at https://nvd.nist.gov/vuln/detail/CVE-2026-94274 before closing the finding.
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
YayReviews is a WordPress plugin that collects and displays customer product or service reviews, storing reviewer-submitted fields such as email address and the review body alongside a moderation state. Vulnerability class CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) arises here from a missing authorization check on a WordPress REST API route: routes registered through register_rest_route() require an effective permission_callback, and a route that returns review objects with a permissive or absent callback is reachable by any anonymous HTTP client. Because the handler returns single review records directly from the datastore rather than filtering on post_status or approval state, pending-moderation submissions are exposed alongside published ones, turning the endpoint into an enumeration and harvesting surface for reviewer PII. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) confirms the flaw is network-reachable and requires no privileges, with impact scoped to confidentiality of review data; the low confidentiality rating reflects the limited data class (review metadata and email addresses) rather than any network or server-level compromise. EUVD tracks the same issue as EUVD-2026-89624, and the reporter of record is contact@wpscan.com, consistent with a WordPress-ecosystem discovery.
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:N/UI:N/S:U/C:L/I:N/A:N
Unauthenticated network access to an unrestricted API route (PR:N/AV:N/AC:L) yields disclosure of limited PII only, so C:L with no integrity or availability impact.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
3DescriptionCVE.org
The YayReviews WordPress plugin before 1.4.1 does not restrict access to an API route that returns individual customer review records, including reviews still pending moderation, allowing unauthenticated attackers to harvest reviewers' email addresses and other non-public review content.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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
Exploit-DB