{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-15010 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-15010 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-15010 is a medium-severity cross-site scripting vulnerability in robin-w bbp style pack, published on 11 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-15010 and fix it if it is affected.\n\nWhat it is: CVE-2026-15010 is a medium-severity cross-site scripting vulnerability in robin-w bbp style pack, published on 11 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-15010 in the wild and no public exploit code.\n\nAffected product: robin-w bbp style pack. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-15010/ (Markdown: https://insights.sbomify.com/CVE-2026-15010/index.md)","id":"CVE-2026-15010","markdown":"https://insights.sbomify.com/CVE-2026-15010/index.md","name":"CVE-2026-15010","record":{"aliases":["GHSA-qv97-pgw5-6f6x"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers can inject arbitrary scripts via topic form fields, leading to code execution and potential account takeover for site visitors.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"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 \u003cspan\u003e 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"bbp style pack \u003c= 6.4.5 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Topic Form Additional Fields","id":"CVE-2026-15010","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Customer Support Ticket System \u0026 Helpdesk \u003c= 6.0.5 - Unauthenticated Code Injection via 'path' Parameter","id":"CVE-2026-15011"},"packages":[],"prev":{"headline":"Advanced File Manager \u003c= 5.4.12 - Reflected Cross-Site Scripting via postMessage 'soundFile' Parameter","id":"CVE-2026-15009"},"products":["bbp style pack"],"published":"2026-07-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-13","vendors":["robin-w"]},"summary":"Authenticated attackers can inject arbitrary scripts via topic form fields, leading to code execution and potential account takeover for site visitors.","url":"https://insights.sbomify.com/CVE-2026-15010/"}