{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-100720 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-100720 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-100720 is a critical cross-site scripting vulnerability in froxlor, published on 26 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-100720 and fix it if it is affected.\n\nWhat it is: CVE-2026-100720 is a critical cross-site scripting vulnerability in froxlor, published on 26 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-100720 in the wild and no public exploit code.\n\nAffected product: froxlor. 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-100720/ (Markdown: https://insights.sbomify.com/CVE-2026-100720/index.md)","id":"CVE-2026-100720","markdown":"https://insights.sbomify.com/CVE-2026-100720/index.md","name":"CVE-2026-100720","record":{"aliases":["GHSA-89vj-gqqr-73p8","GHSA-mmqp-fgp4-5q7j"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Froxlor hosting panel","requires_auth":"low_privilege","summary":"Stored XSS in Froxlor allows customers to execute scripts in admin sessions via SSL certificate issuer fields, leading to account takeover and potential root code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Froxlor 2.0.0 through 2.3.10 is vulnerable to stored cross-site scripting. When a customer (the lowest-privileged authenticated role) uploads an SSL certificate for one of their own domains, the Certificates API add()/update() methods parse it with openssl_x509_parse() and store the issuer organization (issuer['O']) value verbatim without sanitization. Froxlor's table-listing renderer then emits scalar cells through Twig's `raw` filter, disabling HTML auto-escaping, so when an administrator or reseller opens Domains \u003e SSL certificates the attacker-supplied issuer value executes as script in the privileged user's session. This crosses a privilege boundary from customer to admin and can result in full administrator account takeover; because a Froxlor admin controls webserver, DNS, and PHP configuration applied by a cron job running as root, the issue can be further escalated to command execution as root on the managed server. The issue is fixed in Froxlor 2.3.12.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Froxlor before 2.3.12 Stored XSS via SSL certificate issuer","id":"CVE-2026-100720","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"vm2 before 3.12.2 Authorization Bypass via Custom Resolver","id":"CVE-2026-100721"},"packages":[],"prev":{"headline":"Froxlor before 2.3.12 Credential Disclosure via DirProtections API","id":"CVE-2026-100719"},"products":["froxlor"],"published":"2026-09-26","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":"total"},"state":"PUBLISHED","updated":"2026-09-26","vendors":["froxlor"]},"summary":"Stored XSS in Froxlor allows customers to execute scripts in admin sessions via SSL certificate issuer fields, leading to account takeover and potential root code execution.","url":"https://insights.sbomify.com/CVE-2026-100720/"}