CVE-2026-100720

HIGHPre-NVD 8.78.7—
EchelonGraph scoreHIGH confidence

Score 8.7 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-26. A secondary CVSS source baseline 8.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 > 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.

CVSS v3
8.7
EG Score
8.7HIGHhigh confidence
EG Risk
39
EG Risk 39/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 26, 2026

Last Modified

September 26, 2026

Advisory Details (2)

Auto-updated Sep 26, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Froxlor before 2.3.12 Stored XSS via SSL certificate issuer | Advisories | VulnCheck

https://www.vulncheck.com/advisories/froxlor-before-2.3.12-stored-xss-via-ssl-certificate-issuer
github Patch Available🟡 PoC Available

Stored XSS via SSL certificate issuer enables customer-to-admin account takeover in Froxlor 2.x · Advisory · froxlor/froxlor · GitHub

https://github.com/froxlor/froxlor/security/advisories/GHSA-89vj-gqqr-73p8

Vendor Advisories for CVE-2026-100720(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 26× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 12:15 UTCGHSA enrichment
  2. 2026-10-04 00:15 UTCEG score recompute
  3. 2026-10-04 00:15 UTCGHSA enrichment
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-03 12:16 UTCGHSA enrichment
  6. 2026-10-03 00:16 UTCEG score recompute
  7. 2026-10-03 00:16 UTCGHSA enrichment
  8. 2026-10-02 12:15 UTCGHSA enrichment
  9. 2026-10-02 00:14 UTCEG score recompute
  10. 2026-10-02 00:14 UTCGHSA enrichment
  11. 2026-10-01 19:49 UTCEPSS rescore
  12. 2026-10-01 12:14 UTCGHSA enrichment
  13. 2026-10-01 00:15 UTCEG score recompute
  14. 2026-10-01 00:15 UTCGHSA enrichment
  15. 2026-09-30 15:02 UTCEPSS rescore
  16. 2026-09-30 11:47 UTCGHSA enrichment
  17. 2026-09-29 23:47 UTCEG score recompute
  18. 2026-09-29 23:47 UTCGHSA enrichment
  19. 2026-09-29 15:20 UTCEPSS rescore
  20. 2026-09-29 11:23 UTCGHSA enrichment
  21. 2026-09-28 23:21 UTCEG score recompute
  22. 2026-09-28 23:21 UTCGHSA enrichment
  23. 2026-09-28 13:50 UTCEPSS rescore
  24. 2026-09-28 11:21 UTCGHSA enrichment
  25. 2026-09-27 23:21 UTCEG score recompute
Show 8 more
  1. 2026-09-27 23:21 UTCGHSA enrichment
  2. 2026-09-27 11:21 UTCEG score recompute
  3. 2026-09-27 11:20 UTCGHSA enrichment
  4. 2026-09-26 23:17 UTCEG score recompute
  5. 2026-09-26 23:17 UTCGHSA enrichment
  6. 2026-09-26 14:25 UTCEG score recompute
  7. 2026-09-26 13:33 UTCEG score recompute
  8. 2026-09-26 13:30 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100720?
CVE-2026-100720 is a high vulnerability published on September 26, 2026. 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 opensslx509parse() and store the issuer…
When was CVE-2026-100720 disclosed?
CVE-2026-100720 was first published on September 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100720 actively exploited?
CVE-2026-100720 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100720?
CVE-2026-100720 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100720?
A fix for CVE-2026-100720 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100720 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-100720

Explore →

Is Your Infrastructure Affected by CVE-2026-100720?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs