CVE-2026-81919

MEDIUMNVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory (severity: LOW) published 2026-09-15. 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 below 9.5.3 did not validate an anti-CSRF token on the block-arrangement backend endpoint (the arrange() action of Concrete\Controller\Backend\Page\ArrangeBlocks). The action enforced page-edit authorization but performed no token check, and its route accepted any HTTP method, so an attacker could induce a signed-in content editor into loading an attacker-controlled page that auto-submitted a cross-site request and reordered or moved blocks in the draft version of a page the victim was permitted to edit. The default null cookie SameSite configuration let the victim's session cookie accompany the forged request. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 2.3 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/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
3%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 18, 2026

References (1)

Vendor Advisories for CVE-2026-81919(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 17× in last 7d / 24× 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-24 14:04 UTCEPSS rescore
  2. 2026-09-24 12:14 UTCEG score recompute
  3. 2026-09-24 12:14 UTCGHSA enrichment
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-23 12:51 UTCGHSA enrichment
  6. 2026-09-22 13:29 UTCEG score recompute
  7. 2026-09-22 13:29 UTCGHSA enrichment
  8. 2026-09-21 21:09 UTCEPSS rescore
  9. 2026-09-21 14:05 UTCGHSA enrichment
  10. 2026-09-20 14:42 UTCEG score recompute
  11. 2026-09-20 14:42 UTCGHSA enrichment
  12. 2026-09-19 15:12 UTCEG score recompute
  13. 2026-09-19 15:12 UTCGHSA enrichment
  14. 2026-09-18 19:28 UTCEPSS rescore
  15. 2026-09-18 15:50 UTCEG score recompute▲ 2.00
  16. 2026-09-18 15:49 UTCGHSA enrichment
  17. 2026-09-18 15:43 UTCNVD updateCVSS v3 → 4.3 · severity → MEDIUM
  18. 2026-09-16 19:23 UTCEG score recompute
  19. 2026-09-16 19:23 UTCGHSA enrichment
  20. 2026-09-16 14:08 UTCEPSS rescore
  21. 2026-09-15 20:42 UTCEG score recompute
  22. 2026-09-15 19:37 UTCEG score recompute
  23. 2026-09-15 18:38 UTCEG score recompute
  24. 2026-09-15 18:37 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81919?
CVE-2026-81919 is a medium vulnerability published on September 15, 2026. Concrete CMS below 9.5.3 did not validate an anti-CSRF token on the block-arrangement backend endpoint (the arrange() action of Concrete\Controller\Backend\Page\ArrangeBlocks). The action enforced page-edit authorization but performed no token check, and its route accepted any HTTP method, so an…
When was CVE-2026-81919 disclosed?
CVE-2026-81919 was first published in the National Vulnerability Database on September 15, 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-81919 actively exploited?
CVE-2026-81919 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 96.6% of all scored CVEs.
What is the CVSS score of CVE-2026-81919?
CVE-2026-81919 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-81919?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81919, 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-81919

Explore →

Is Your Infrastructure Affected by CVE-2026-81919?

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

Book a Demo →Browse All CVEs