CVE-2026-107657: HivePress <= 1.7.31 - Unauthenticated Stored Cross-Site Scripting via Custom User Attribute Value via Registration Form

Published Oct 10, 2026
·
Updated

The HivePress – Business Directory, Listings & Classified Ads Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the '<custom user attribute field name, e.g. profiletest>' parameter in all versions up to, and including, 1.7.31 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires an administrator to have configured a text-type custom user attribute whose display format places %value% inside an HTML attribute context (e.g., the documented pattern &lt;a href="%value%"&gt;Custom link&lt;/a&gt;), and for front-end user profiles to be enabled — both of which reflect the plugin's standard, documented configuration.

Affected Software

1 affected component
HivePress HivePress WordPress Plugin<=1.7.31

Event History

Oct 10, 2026
CVE Published
via MITRE·08:26 AM
Data Sourced
via MITRE·08:26 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to exploitation?

Deployments are exposed when they run HivePress 1.7.31 or earlier, have front-end user profiles enabled, and define a text-type custom user attribute whose display format inserts %value% into an HTML attribute. The example documented format is <a href="%value%">Custom link</a>.

2

Does an attacker need an account or user interaction to inject the payload?

No. The vulnerability can be exploited by an unauthenticated attacker through the registration form, with no user interaction required for injection.

3

When does the injected script execute?

The payload is stored and executes when a user accesses a page containing the injected value. Its impact includes potential disclosure or modification of data in the affected user's browser context.

4

What configuration change can reduce exposure if patching is delayed?

Disable front-end user profiles or remove/avoid text-type custom user attributes whose display formats place %value% inside an HTML attribute context. These conditions are required for the described exploitation path.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203