Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister subscriber-level account
-
ExploitInject script via custom text attribute field
-
ExecutionMalicious value stored in listing attribute
-
ImpactScript executes when users view injected page
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 | Two conditions must hold simultaneously: (1) the attacker holds an authenticated subscriber-level (or higher) account, implying the site permits user registration/listing submission; and (2) an administrator has configured a HivePress Text attribute whose display format places the %value% token inside an HTML attribute (e.g. title="%value%") - a documented but non-default HivePress pattern. Exploitation is NOT possible against a default configuration where %value% is rendered as normal element text. Limiting factors: requires valid authentication (not anonymous), requires that specific attribute display configuration, affects only versions ≤1.7.31 (fixed in 1.7.32), and the payload fires only when a user subsequently views the injected page. |
| Impact | This is a moderate-risk, conditionally-exploitable stored XSS (CWE-79) rather than a top-tier emergency. The Wordfence CVSS 3.1 vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N, base 6.4) indicates a network-reachable, low-privilege (PR:L, i.e. authenticated subscriber-and-above) flaw with scope change (S:C) reflecting script execution in other users' browser contexts, with limited confidentiality/integrity impact and no availability impact. No EPSS score, KEV listing, or public POC was provided in the input, so exploitation status is: no public exploit identified at time of analysis. The signals are internally consistent (low privilege, limited impact, no active-exploitation evidence), but one caveat matters: the description states exploitation is ONLY possible when an administrator has configured a Text attribute whose display format embeds the %value% token inside an HTML attribute (e.g. title="%value%"). This non-default precondition is not reflected in the AC:L rating; a more honest reading raises attack complexity because a required condition lies outside the attacker's control. Net: a genuine but gated vulnerability - a real priority only for sites that both allow self-registration (subscriber accounts) and use that specific attribute display configuration. Verify your own configuration before treating it as high priority. |
| Exploit ScenarioDerived | An attacker registers a free subscriber account on a HivePress-powered directory site whose administrator has configured a Text attribute rendering %value% inside an HTML attribute. The attacker submits a user-defined field value containing a payload that breaks out of the HTML attribute context; it is stored unsanitized and then executes in the browser of any visitor - including administrators - who views the affected page. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Stored cross-site scripting in the HivePress WordPress plugin (Business Directory, Listings & Classified Ads) affects all versions up to and including 1.7.31 and allows authenticated users with subscriber-level accounts or higher to inject arbitrary JavaScript that executes when other users view the affected listing page. Exploitation is conditional, not universal: the site must permit subscriber-level registration or listing submission, and an administrator must have configured a HivePress Text attribute whose display format places the %value% token inside an HTML attribute (for example title="%value%"), which is a documented but non-default HivePress pattern - a default configuration that renders %value% as normal element text is not exploitable. The vendor has released 1.7.32, which includes the fix for escaping field and token values; no public exploit code has been identified at time of analysis, and the flaw is not confirmed actively exploited (CISA KEV). Independent assessment rates the practical severity as moderate and conditionally exploitable, with attack complexity assessed as High (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N) rather than the published AC:L rating.
RemediationAI
Vendor-released patch: 1.7.32 - upgrade the HivePress plugin to 1.7.32 or later, which explicitly 'Fixed escaping field and token values' according to the release notes at https://github.com/hivepress/hivepress/releases/tag/1.7.32 and is referenced alongside the advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/723322ab-2ad0-42e2-b518-0987d9203c49?source=cve. If immediate upgrade is not possible, apply targeted compensating controls in this order: first, audit every HivePress Text attribute display format under Listings/Attributes and remove any %value% token placed inside an HTML attribute (such as title="%value%" or placeholder="%value%"), moving it to element text content instead - this is the exact configuration the exploit depends on, and the trade-off is only cosmetic, since attribute-positioned values will render as body text rather than tooltips or attributes; second, restrict who can create listings by disabling subscriber-level registration or gating listing submission behind a moderated role, which removes the injection vector at the cost of reducing directory participation; third, review existing listings for stored script payloads and remove or sanitize them, since patching alone does not clean already-injected content. Note that a WAF rule blocking script markup in listing submissions adds defense in depth but may produce false positives on legitimate listings containing angle brackets, and does not remove payloads already persisted in the database. After upgrading, re-verify that custom display formats remain correct, as the 1.7.32 escaping change may alter output for formats that previously relied on unescaped token substitution.
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 root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation / Cross-Site Scripting), specifically a stored variant inside a WordPress plugin that implements a custom field/token templating layer. HivePress lets administrators define attributes - including Text attributes - with a display format string in which tokens such as %value% are substituted with user-supplied listing content. When that format places %value% inside an HTML attribute context (e.g. title="%value%"), the user-controlled value is emitted without adequate context-aware escaping, so injected characters can break out of the attribute and introduce script markup that is persisted with the listing and executed in the browser of any subsequently viewing user. The referenced source paths (includes/fields/class-field.php, includes/helpers.php, includes/blocks/class-attributes.php, includes/fields/class-text.php, includes/controllers/class-listing.php in tag 1.7.31) show where field rendering, token substitution and listing attribute handling occur; the 1.7.32 release note 'Fixed escaping field and token values' confirms the fix is an output-escaping hardening of that token pipeline rather than a control-flow change. Because the payload is stored and observer-triggered, the affected component is the rendering layer shared across listing pages, blocks and attribute renderers. The CPE string cpe:2.3:a:hivepress:hivepress_-_business_directory,_listings_&_classified_ads_plugin:*:*:*:*:*:*:*:* confirms the plugin itself (not the WordPress core) is the vulnerable product, with the wildcard indicating all tracked versions at the time of publication. The CVSS scope-change component (S:C) reflects that injected script executes in the security context of the victim's session on the WordPress site, potentially reaching beyond the original vulnerable component's privileges.
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
AV:N and PR:L (authenticated subscriber) match the advisory, but AC:H reflects the required non-default admin configuration (%value% inside an HTML attribute) outside the attacker's control; S:C with C:L/I:L/A:N captures cross-user script execution.
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 'custom text attribute (user-defined field name)' parameter in all versions up to, and including, 1.7.31 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. This is only exploitable when an administrator has configured a Text attribute whose display format places the %value% token inside an HTML attribute (e.g., title="%value%"), which is a documented HivePress pattern.
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-96097
GHSA-82fv-q4vm-rv8c
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB