Joomla Extension - j2commerce.com - Any order can be marked Failed by anyone in J2Store 1.0.0-3.3.2, 4.0.0-4.0.22, 4.1.0-4.1.7 - Unauthenticated denial-of-service against the order pipeline: mass-failing pending orders to disrupt revenue and force manual reprocessing, or flipping already-fulfilled orders back to FAILED to cause operational confusion (unwarranted refunds/cancellations, customer-support load). Unlike the earlier confirmation-fraud issue, this required no correct payment amount or transaction data at all.
CVE-2026-82189
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(medium)
- EG Risk
- 54(Track)EG Risk 54/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 computedSeverity87% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 16, 2026
Advisory Details (1)
Auto-updated Sep 15, 2026Vendor Advisories for CVE-2026-82189(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 19× in last 7d / 19× 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.
- 2026-09-19 04:03 UTCEG score recompute
- 2026-09-19 04:03 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 16:55 UTCGHSA enrichment
- 2026-09-18 05:46 UTCEG score recompute
- 2026-09-18 05:46 UTCGHSA enrichment
- 2026-09-17 18:37 UTCGHSA enrichment
- 2026-09-17 06:42 UTCGHSA enrichment
- 2026-09-16 19:33 UTCEG score recompute
- 2026-09-16 19:33 UTCGHSA enrichment
- 2026-09-16 17:54 UTCEG score recompute
- 2026-09-16 17:54 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 06:04 UTCEG score recompute
- 2026-09-16 06:04 UTCGHSA enrichment
- 2026-09-15 20:41 UTCEG score recompute
- 2026-09-15 19:32 UTCEG score recompute
- 2026-09-15 19:00 UTCEG score recompute
- 2026-09-15 18:57 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-82189?
When was CVE-2026-82189 disclosed?
Is CVE-2026-82189 actively exploited?
What is the CVSS score of CVE-2026-82189?
How do I remediate CVE-2026-82189?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82189
Is Your Infrastructure Affected by CVE-2026-82189?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.