{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-101925 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-101925 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-101925 is a medium-severity cross-site scripting vulnerability in robin-w bbp style pack, published on 1 Oct 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-101925 and fix it if it is affected.\n\nWhat it is: CVE-2026-101925 is a medium-severity cross-site scripting vulnerability in robin-w bbp style pack, published on 1 Oct 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-101925 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-101925/ (Markdown: https://insights.sbomify.com/CVE-2026-101925/index.md)","id":"CVE-2026-101925","markdown":"https://insights.sbomify.com/CVE-2026-101925/index.md","name":"CVE-2026-101925","record":{"aliases":["GHSA-3qmp-qqq9-w2h8"],"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 subscribers can inject arbitrary scripts via display names in bbPress replies, potentially leading to session hijacking or malicious actions.","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 via the 'display_name (via /wp-admin/profile.php) + bbp_reply_content (via bbPress reply form)' parameter in all versions up to, and including, 6.4.8 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. Successful exploitation requires the attacker to wrap their crafted reply in a \u0026lt;pre\u0026gt; block, which prevents WordPress's wpautop/wptexturize processors from converting straight double quotes in the stored display name into typographic curly-quote entities that would otherwise neutralize the attribute-injection.","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.8 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Author Display Name","id":"CVE-2026-101925","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"SQL injection in Hyyan WooCommerce Polylang Integration","id":"CVE-2026-101926"},"packages":[],"prev":{"headline":"NewStatPress \u003c= 1.4.5 - Unauthenticated Stored Cross-Site Scripting via 'urlrequested' Attribute via Query String","id":"CVE-2026-101924"},"products":["bbp style pack"],"published":"2026-10-01","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-10-01","vendors":["robin-w"]},"summary":"Authenticated subscribers can inject arbitrary scripts via display names in bbPress replies, potentially leading to session hijacking or malicious actions.","url":"https://insights.sbomify.com/CVE-2026-101925/"}