Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister/authenticate as subscriber
-
DeliverySubmit listing with malicious 'message' payload
-
ExploitPayload stored without sanitization
-
ExecutionVictim logs in via embedded form
-
ImpactScript executes in victim's browser session
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires three concrete conditions: (1) the attacker holds at least subscriber-level authenticated access (PR:L) on the target site; (2) the site administrator has enabled the user listing submission feature - a non-default deployment setting without which the attack surface does not exist; and (3) a victim subsequently logs in via the embedded login form on the attacker-controlled listing page, at which point the stored payload in the 'message' parameter executes. Limiting factors: the required subscriber authentication, the required non-default listing-submission configuration, and the dependency on a victim interacting with/logging in on the malicious listing page all meaningfully constrain realistic exploitation despite the network attack vector. |
| Impact | This is a medium-severity stored XSS (CVSS 6.4, CWE-79) that should be treated as a moderate, conditional priority rather than an urgent emergency. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N indicates network-reachable, low-complexity exploitation, but PR:L confirms the attacker must already hold subscriber-level (authenticated) access - this is NOT an unauthenticated flaw. The scope change (S:C) and low confidentiality/integrity impact correctly reflect that injected script executes in a different security context (another user's authenticated session/browser). No EPSS score, CISA KEV listing, or POC is present in the provided data, so there is no public exploit identified at time of analysis and no evidence of active exploitation. Crucially, the description adds a limiting condition absent from the raw CVSS: exploitation only works when the administrator has enabled user listing submission - a non-default dependency that materially reduces real-world exploitability and arguably warrants higher attack complexity than AC:L suggests. Net: a legitimate issue worth patching on normal cadence, but the authentication requirement plus the required non-default configuration make it lower real-world risk than the network/low-complexity metrics alone imply. |
| Exploit ScenarioDerived | An attacker registers a free subscriber account on a HivePress site that allows user listing submissions, then submits a listing whose 'message' parameter carries a malicious script payload that is stored unsanitized. When a victim later logs in via the embedded form on the attacker's listing page, the stored script executes in the victim's authenticated browser session, enabling session/credential theft or actions on the victim's behalf. No public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
Stored cross-site scripting in the HivePress - Business Directory, Listings & Classified Ads plugin for WordPress (all versions up to and including 1.7.32) allows an authenticated attacker with subscriber-level access or above to inject arbitrary web scripts through the 'message' parameter, which are then rendered to other users. Exploitation is conditional: the site administrator must have enabled user listing submission (a non-default setting), and a victim must subsequently log in through the login form embedded on the attacker's listing page for the payload to execute in their browser. This is a medium-severity issue (CVSS 6.4, CWE-79); no public exploit code was identified at time of analysis and there is no CISA KEV confirmation of active exploitation, so it should be treated as a moderate, conditional priority rather than an emergency.
RemediationAI
Upgrade the HivePress plugin to version 1.8.0 or later - the vendor-released patch, obtainable through the WordPress plugin update mechanism or from https://plugins.trac.wordpress.org/changeset?reponame=&new=3747070%40hivepress%2Ftags%2F1.8.0&old=3732142%40hivepress%2Ftags%2F1.7.32, and documented alongside the upstream fix at https://github.com/hivepress/hivepress/pull/374/changes/508b1766beb79949ab22dd4a163fafadb4c63e7d and the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/5d1937ae-d350-452c-b20e-d85bc88dbe48?source=cve. If immediate patching is not possible, the most effective compensating control is to disable the user listing submission feature, which removes the vulnerable attack surface entirely - the trade-off being that legitimate user-submitted listings can no longer be created; alternatively, restrict or disable public subscriber registration, or require administrative moderation/approval of submissions before they are published, though this adds operational overhead and does not fix the underlying missing escaping. Deploying a web application firewall rule targeting stored script payloads in listing message fields, or a Content Security Policy that blocks inline script execution, can reduce exploitability but may break legitimate site functionality and should be treated only as temporary mitigations. Sites that cannot determine whether user listing submission was ever enabled should verify the plugin setting and audit existing listings for injected script content before upgrading.
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 is a CWE-79 improper neutralization of input during web page generation (stored/persistent XSS) in a WordPress plugin. HivePress implements its own form rendering and data-binding layer - the referenced source files (includes/forms/class-form.php, includes/blocks/class-form.php, includes/components/class-editor.php, and assets/js/common.js) handle form field setup, block rendering, and editor output - and the 'message' field submitted as part of a listing is stored and later echoed back into HTML without adequate sanitization on input and escaping on output. The CVSS vector AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N confirms the attack is network-reachable with low complexity, requires low privilege (subscriber), and has changed scope (S:C), meaning the injected script executes in the context of the WordPress site beyond the plugin's own security boundary, but with only low confidentiality and integrity impact and no availability impact. The upstream fix in release 1.8.0 (changeset 3747070, replacing 1.7.32) and PR #374 / commit 508b1766beb79949ab22dd4a163fafadb4c63e7d harden the form and admin handling code, including added nonce verification, capability checks on meta boxes, and explicit escaping/sanitization annotations around form value handling and output.
Know when Wordpress Plugin 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:C/C:L/I:L/A:N
Network-reachable stored XSS requiring subscriber authentication (PR:L); payload auto-executes in a different user's session (S:C, UI:N) with limited confidentiality/integrity impact and no availability effect.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The HivePress - Business Directory, Listings & Classified Ads Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'message' parameter in all versions up to, and including, 1.7.32 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires that the site administrator has enabled user listing submission, and the script executes in the victim's browser at the moment of successful login via the embedded form on the attacker's listing page.
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
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
EUVD-2026-102791
GHSA-8w67-xhw6-gqxx
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB