{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-101920 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-101920 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-101920 is a high-severity cross-site scripting vulnerability in Molongui Authorship – Author Boxes, Guest Authors \u0026 Co-Authors for WordPress, published on 10 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-101920 and fix it if it is affected.\n\nWhat it is: CVE-2026-101920 is a high-severity cross-site scripting vulnerability in Molongui Authorship – Author Boxes, Guest Authors \u0026 Co-Authors for WordPress, published on 10 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-101920 in the wild and no public exploit code.\n\nAffected product: Molongui Authorship – Author Boxes, Guest Authors \u0026 Co-Authors for WordPress. 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-101920/ (Markdown: https://insights.sbomify.com/CVE-2026-101920/index.md)","id":"CVE-2026-101920","markdown":"https://insights.sbomify.com/CVE-2026-101920/index.md","name":"CVE-2026-101920","record":{"aliases":["GHSA-m398-mh86-wgcp"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject arbitrary scripts via comment href attributes in the Molongui Authorship WordPress plugin, leading to stored XSS.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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 Molongui Authorship – Author Boxes, Guest Authors \u0026 Co-Authors for WordPress plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'comment (href attribute inside comment content)' parameter in all versions up to, and including, 5.2.12 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 is exploitable in the free build because the plugin's author-filter rewriter never appends the ?m_bm=true marker to its own anchors (Plugin::has_pro() returns false), meaning every href the byline script selects and rewrites is fully attacker-controlled.","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":"Molongui Authorship \u003c= 5.2.12 - Unauthenticated Stored DOM-Based Cross-Site Scripting via Comment href Attribute","id":"CVE-2026-101920","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"WPForms \u003c= 2.0.2.1 - Reflected Cross-Site Scripting via 'query_var' Smart Tag in iframe srcdoc Attribute","id":"CVE-2026-101921"},"packages":[],"prev":{"headline":"Hypershift: hypershift: unsanitized kubeconfig passthrough from tenant namespace to control plane","id":"CVE-2026-101919"},"products":["Molongui Authorship – Author Boxes, Guest Authors \u0026 Co-Authors for WordPress"],"published":"2026-10-10","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-11","vendors":["molongui"]},"summary":"Unauthenticated attackers can inject arbitrary scripts via comment href attributes in the Molongui Authorship WordPress plugin, leading to stored XSS.","url":"https://insights.sbomify.com/CVE-2026-101920/"}