CVE-2026-78000

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 57% 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).

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

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

Joomla Extension - j2commerce.com - Reflected XSS via filter_tag, pricefrom and priceto in J2Store 1.0.0-3.3.21, 4.0.0-4.0.21, 4.1.0-4.1.6 - Four task handlers accepted a base64-encoded URL from user input and redirected to it without validating the destination host, enabling phishing using the shop's trusted domain. No authentication required.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity53% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

September 3, 2026

Last Modified

September 3, 2026

Advisory Details (1)

Auto-updated Sep 3, 2026
No patch confirmed yet.
generic

Powerful and intuitive Joomla eCommerce. - J2Commerce

https://www.j2commerce.com/

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-78000?
CVE-2026-78000 is a medium vulnerability published on September 3, 2026. Joomla Extension - j2commerce.com - Reflected XSS via filter_tag, pricefrom and priceto in J2Store 1.0.0-3.3.21, 4.0.0-4.0.21, 4.1.0-4.1.6 - Four task handlers accepted a base64-encoded URL from user input and redirected to it without validating the destination host, enabling phishing using the…
When was CVE-2026-78000 disclosed?
CVE-2026-78000 was first published in the National Vulnerability Database on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-78000 actively exploited?
CVE-2026-78000 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.5% of all scored CVEs.
What is the CVSS score of CVE-2026-78000?
CVE-2026-78000 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-78000?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-78000, 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-78000

Explore →

Is Your Infrastructure Affected by CVE-2026-78000?

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

Book a Demo →Browse All CVEs