CVE-2026-81923

LOWNVD 2.72.7—
EchelonGraph scoreHIGH confidence

Score 2.7 from GitHub Security Advisory (severity: LOW) published 2026-09-15. NVD baseline CVSS 2.7; sources differ by 0.0.

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

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

In Concrete CMS before 9.5.3, the SEO Bulk Update Meta Tags editor did not check per-page edit permissions before saving. The saveRecord() action validated the per-page CSRF token but never called canEditPageProperties() for the target page, so a user who was granted access to the bulk SEO tool and could view (but not edit) a given page was able to change that page's meta title, meta description, and URL handle outside their edit scope, tampering with the presentation and live URLs of otherwise protected content. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 2.1 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N. Thanks Andrew Gonzalez for reporting.

CVSS v3
2.7
EG Score
2.7(high)
EG Risk
12(Track)
EG Risk 12/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
Severity27% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 18, 2026

References (1)

Vendor Advisories for CVE-2026-81923(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 13× in last 7d / 20× 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 20:29 UTCEG score recompute
  2. 2026-09-24 20:29 UTCGHSA enrichment
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-22 16:01 UTCEPSS rescore
  6. 2026-09-21 21:09 UTCEPSS rescore
  7. 2026-09-21 18:09 UTCEG score recompute
  8. 2026-09-21 18:09 UTCGHSA enrichment
  9. 2026-09-20 20:16 UTCEPSS rescore
  10. 2026-09-18 19:28 UTCEPSS rescore
  11. 2026-09-18 15:49 UTCEG score recompute▲ 0.60
  12. 2026-09-18 15:48 UTCGHSA enrichment
  13. 2026-09-18 15:43 UTCNVD updateCVSS v3 → 2.7
  14. 2026-09-16 19:23 UTCEG score recompute
  15. 2026-09-16 19:23 UTCGHSA enrichment
  16. 2026-09-16 14:08 UTCEPSS rescore
  17. 2026-09-15 20:41 UTCEG score recompute
  18. 2026-09-15 19:32 UTCEG score recompute
  19. 2026-09-15 19:03 UTCEG score recompute
  20. 2026-09-15 19:02 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81923?
CVE-2026-81923 is a low vulnerability published on September 15, 2026. In Concrete CMS before 9.5.3, the SEO Bulk Update Meta Tags editor did not check per-page edit permissions before saving. The saveRecord() action validated the per-page CSRF token but never called canEditPageProperties() for the target page, so a user who was granted access to the bulk SEO tool and…
When was CVE-2026-81923 disclosed?
CVE-2026-81923 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-81923 actively exploited?
CVE-2026-81923 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 79.8% of all scored CVEs.
What is the CVSS score of CVE-2026-81923?
CVE-2026-81923 has a CVSS v3 base score of 2.7 (NVD).
How do I remediate CVE-2026-81923?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81923, 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-81923

Explore →

Is Your Infrastructure Affected by CVE-2026-81923?

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

Book a Demo →Browse All CVEs