dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-15010

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The bbp Style Pack plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 6.4.5 via the Topic Form Additional Fields feature. This is due to insufficient input sanitization in bsp_topic_fields_form_save() (which writes $_POST['bsp_topic_fields_label{n}'] directly to post meta via update_post_meta() with no filtering) and missing output escaping in bsp_topic_content_append_topic_fields() (which concatenates the stored meta value into an HTML <span> and echoes it via apply_filters/echo without esc_html()). This makes it possible for authenticated attackers, with Subscriber-level access and above (who have bbPress topic-creation privileges), to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page, including unauthenticated visitors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The bbp Style Pack WordPress plugin fails to sanitize user input when saving topic form additional fields and fails to escape the stored data when outputting it. The bsp_topic_fields_form_save() function directly passes $_POST['bsp_topic_fields_label{n}'] to update_post_meta() without sanitization, and bsp_topic_content_append_topic_outputs the unescaped value into an HTML <span> element, allowing Stored XSS injection by authenticated users with Subscriber-level access.

MitigationImplement input sanitization using sanitize_text_field() or similar WordPress sanitization functions in bsp_topic_fields_form_save(), and add output escaping with esc_html() or esc_attr() in bsp_topic_content_append_topic_fields() before echoing values into HTML context.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm bbp Style Pack plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'bbp Style Pack' or check the plugin files in /wp-content/plugins/ for the bbp-style-pack directory. Review the main plugin file (e.g., bbp-style-pack.php) for the version comment header.
    Affected if The plugin is installed and active
  2. Check the plugin version against the fixed release
    Open the main plugin file header to find the Version: X.X.X field. Compare this to any post-fix version that addresses this XSS vulnerability.
    Affected if The installed version predates the patched version that adds sanitization and escaping
  3. Verify topic form additional fields are configured
    In WordPress admin, navigate to the plugin settings where topic form fields can be added (typically under bbPress > Style Pack > Topic Form Fields). Look for any configured custom fields using the bsp_topic_fields_label{n} pattern.
    Affected if Additional topic form fields are enabled and configured with user-defined labels
  4. Inspect stored data in the database for unsanitized content
    Query the wp_postmeta table for meta_key values matching 'bsp_topic_fields_label%'. Use: SELECT * FROM wp_postmeta WHERE meta_key LIKE 'bsp_topic_fields_label%'. Examine the meta_value field for any raw HTML or script tags that were saved without sanitization.
    Affected if Stored field labels contain raw HTML, JavaScript, or unescaped special characters
  5. Check source code for missing sanitization and escaping
    Review the plugin file containing bbp_style_pack() and bsp_topic_content_append_topic_fields() functions. Look for update_post_meta() calls that use $_POST['bsp_topic_fields_label{n}'] without sanitize_text_field() or similar, and echo statements outputting these values without esc_html() or esc_attr().
    Affected if The code passes $_POST data directly to update_post_meta() without sanitization, or echoes stored values without escaping in HTML context

A user is affected if the bbp Style Pack plugin is installed with topic form additional fields enabled, and the code lacks proper input sanitization before storage and output escaping before display, allowing stored XSS via subscriber-level access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement input sanitization using sanitize_text_field() or similar WordPress sanitization functions in bsp_topic_fields_form_save(), and add output escaping with esc_html() or esc_attr() in bsp_topic_content_append_topic_fields() before echoing values into HTML context.

Recommended fix Moderate confidence

Latest version after 6.4.5 (check WordPress plugin repository for 6.4.6 or newer)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the bbp Style Pack plugin
  4. Check if an update is available. If so, update to the latest version (likely 6.4.6 or higher which should contain the security fix)
  5. If no update is available through WordPress, download the latest version from the official WordPress plugin repository at https://wordpress.org/plugins/bbp-style-pack/
  6. Deactivate and delete the current version, then upload and activate the new version
  7. Verify the update was successful by checking the plugin version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15010 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15010 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data