CVE-2026-73318

LOWPre-NVD 3.83.8—
EchelonGraph scoreHIGH confidence

Score 3.8 from GitHub Security Advisory published 2026-09-08. a secondary CVSS source baseline 3.8; sources differ by 0.0.

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

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

XenForo before 2.3.13 contains a missing authorization vulnerability in the force-agreement controller that allows any ACP administrator to access and submit force-agreement forms regardless of their assigned permissions. Attackers can bypass the option permission declared in the navigation configuration to update the global policy last-updated timestamp, forcing all users to re-agree to the privacy policy or terms of service.

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

Published

September 8, 2026

Last Modified

September 14, 2026

References (5)

Vendor Advisories for CVE-2026-73318(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 8× in last 7d / 29× 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-23 23:36 UTCEG score recompute
  2. 2026-09-23 23:36 UTCGHSA enrichment
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-21 21:09 UTCEPSS rescore
  5. 2026-09-20 22:33 UTCEG score recompute
  6. 2026-09-20 22:33 UTCGHSA enrichment
  7. 2026-09-20 20:16 UTCEPSS rescore
  8. 2026-09-18 19:28 UTCEPSS rescore
  9. 2026-09-17 21:30 UTCEG score recompute
  10. 2026-09-17 21:30 UTCGHSA enrichment
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-15 03:12 UTCEPSS rescore
  14. 2026-09-14 20:27 UTCEG score recompute
  15. 2026-09-14 20:27 UTCGHSA enrichment
  16. 2026-09-14 19:40 UTCEG score recompute
  17. 2026-09-14 19:40 UTCGHSA enrichment
  18. 2026-09-12 15:02 UTCEPSS rescore
  19. 2026-09-11 20:47 UTCEG score recompute
  20. 2026-09-11 20:47 UTCGHSA enrichment
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-10 09:35 UTCEPSS rescore
  23. 2026-09-09 01:18 UTCEG score recompute
  24. 2026-09-09 01:18 UTCGHSA enrichment
  25. 2026-09-08 20:12 UTCEG score recompute
Show 4 more
  1. 2026-09-08 20:12 UTCGHSA enrichment
  2. 2026-09-08 14:30 UTCEG score recompute
  3. 2026-09-08 13:25 UTCEG score recompute
  4. 2026-09-08 13:24 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73318?
CVE-2026-73318 is a low vulnerability published on September 8, 2026. XenForo before 2.3.13 contains a missing authorization vulnerability in the force-agreement controller that allows any ACP administrator to access and submit force-agreement forms regardless of their assigned permissions. Attackers can bypass the option permission declared in the navigation…
When was CVE-2026-73318 disclosed?
CVE-2026-73318 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73318 actively exploited?
CVE-2026-73318 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 60.5% of all scored CVEs.
What is the CVSS score of CVE-2026-73318?
CVE-2026-73318 has a CVSS v3 base score of 3.8 (NVD).
How do I remediate CVE-2026-73318?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73318, 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-73318

Explore →

Is Your Infrastructure Affected by CVE-2026-73318?

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

Book a Demo →Browse All CVEs