CVE-2026-81916

MEDIUMNVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-09-11. NVD baseline CVSS 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Concrete CMS before 9.5.3 evaluated the authorization check for an Express entry submission against the entity of the posted form rather than the entity identified by the dashboard route. As a result, a user permitted to add entries to one Express object could create entries in a different Express object outside their authorization scope, potentially polluting protected datasets, triggering workflows, or injecting content into administrative processes. The dashboard submit route resolved the mutated entity from the attacker-controlled route ID while the permission check validated the independently posted form's entity, and the submission proceeded because the two entities were never compared. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 5.1 with vector CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N. Thanks Yonatan Drori from Tenzai for reporting.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
19(Track)
EG Risk 19/100SSVC: Track

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
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

September 11, 2026

Last Modified

September 18, 2026

References (1)

Vendor Advisories for CVE-2026-81916(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 31× 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-09-20 20:16 UTCEPSS rescore
  2. 2026-09-20 16:08 UTCGHSA enrichment
  3. 2026-09-19 15:58 UTCEG score recompute
  4. 2026-09-19 15:58 UTCGHSA enrichment
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 15:49 UTCEG score recompute▼ 0.80
  7. 2026-09-18 15:49 UTCGHSA enrichment
  8. 2026-09-18 15:43 UTCNVD updateCVSS v3 → 4.3
  9. 2026-09-18 15:16 UTCEG score recompute
  10. 2026-09-18 15:16 UTCGHSA enrichment
  11. 2026-09-17 15:11 UTCGHSA enrichment
  12. 2026-09-16 15:06 UTCEG score recompute
  13. 2026-09-16 15:06 UTCGHSA enrichment
  14. 2026-09-16 14:08 UTCEPSS rescore
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-15 15:01 UTCGHSA enrichment
  17. 2026-09-15 13:34 UTCEG score recompute
  18. 2026-09-15 13:34 UTCGHSA enrichment
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-14 13:29 UTCEG score recompute
  22. 2026-09-14 13:29 UTCGHSA enrichment
  23. 2026-09-14 13:10 UTCEG score recompute
  24. 2026-09-14 13:10 UTCGHSA enrichment
  25. 2026-09-13 20:46 UTCEG score recompute
Show 6 more
  1. 2026-09-13 20:46 UTCGHSA enrichment
  2. 2026-09-12 20:41 UTCEG score recompute
  3. 2026-09-12 20:41 UTCGHSA enrichment
  4. 2026-09-11 20:36 UTCEG score recompute
  5. 2026-09-11 20:14 UTCEG score recompute
  6. 2026-09-11 20:13 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81916?
CVE-2026-81916 is a medium vulnerability published on September 11, 2026. Concrete CMS before 9.5.3 evaluated the authorization check for an Express entry submission against the entity of the posted form rather than the entity identified by the dashboard route. As a result, a user permitted to add entries to one Express object could create entries in a different Express…
When was CVE-2026-81916 disclosed?
CVE-2026-81916 was first published in the National Vulnerability Database on September 11, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81916 actively exploited?
CVE-2026-81916 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.1% of all scored CVEs.
What is the CVSS score of CVE-2026-81916?
CVE-2026-81916 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-81916?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81916, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-81916?

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

Start Free Scan →Browse All CVEs