CVE-2026-132124

MEDIUMPre-NVD 4.84.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 4.8 from GitHub Security Advisory (severity: MODERATE) published 2026-11-18. A secondary CVSS source baseline 4.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-128621 (ENISA EUVD) · GHSA-q7jr-f9xr-c54g (GitHub Security Advisories)Source: ENISA EUVD

4.8EG
EchelonGraph verdictMonitorThe upstream fix is not in a release yet: until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.8Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

modified eCommerce Shopsoftware through 3.3.0 contains a stored cross-site scripting vulnerability that allows authenticated administrators to inject scripts via the orders_status_name parameter in admin/orders_status.php. Attackers with per-page order status access can store payloads that execute in other administrators' browsers when the unencoded status name is displayed.

CVSS
4.8
EG Score
4.8MEDIUMhigh confidence
EG Risk
22
EG Risk 22/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity48% × 45%
Impact severity (EG Severity): CVSS 4.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it.
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.8): severity, escalated by confirmed exploitation. This CVE's 4.8 is its impact severity (EG Severity), not escalated.

EG Severity
4.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-20). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 18, 2026

Last Modified

November 21, 2026

Advisory Details (4)

Auto-updated Nov 18, 2026
🔬 Proof of concept available. Upstream fix merged — awaiting tagged release. Sources: github_pr.
Web page

modified eCommerce Shopsoftware through 3.3.0 Stored XSS via admin/orders_status.php | Advisories | VulnCheck

https://www.vulncheck.com/advisories/modified-ecommerce-shopsoftware-through-3.3.0-stored-xss-via-admin-orders-status-php
Web page

GitHub - modified-shop/modified-shop: Open-source eCommerce shop system based on PHP & MySQL - maintained by the community and continuously modernized for real-world online stores. · GitHub

https://github.com/modified-shop/modified-shop
Web page🟡 PoC Available

Advisory/modified_shopsoftware-SXSS-orders_status.md at main · vinniboy021-blip/Advisory · GitHub

https://github.com/vinniboy021-blip/Advisory/blob/main/modified_shopsoftware-SXSS-orders_status.md
GitHub pull request

Remove active content from shop texts saved in the admin

Fix merged in modified-shop/modified-shop PR #3748 on 2026-11-18 — awaiting tagged release

https://github.com/modified-shop/modified-shop/pull/3748

Vendor Advisories for CVE-2026-132124(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 9× in last 7d / 9× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  2. 2026-11-21 04:28 UTCEchelonGraph re-scored
  3. 2026-11-21 04:28 UTCGHSA enrichmentGHSA-q7jr-f9xr-c54g · GitHub severity MODERATE · GitHub CVSS 4.8
  4. 2026-11-21 03:47 UTCEchelonGraph re-scored
  5. 2026-11-21 03:47 UTCGHSA enrichmentGHSA-q7jr-f9xr-c54g · GitHub severity MODERATE · GitHub CVSS 4.8
  6. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  7. 2026-11-20 05:47 UTCEchelonGraph re-scored
  8. 2026-11-20 05:47 UTCGHSA enrichmentGHSA-q7jr-f9xr-c54g · GitHub severity MODERATE · GitHub CVSS 4.8
  9. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  10. 2026-11-18 15:47 UTCEchelonGraph re-scored
  11. 2026-11-18 15:47 UTCGHSA enrichmentGHSA-q7jr-f9xr-c54g · GitHub severity MODERATE · GitHub CVSS 4.8
  12. 2026-11-18 13:28 UTCEchelonGraph re-scored
  13. 2026-11-18 13:03 UTCENISA EUVD ID recordedEUVD-2026-128621 · Source: ENISA EUVD
  14. 2026-11-18 12:23 UTCEchelonGraph re-scoredFirst assessed: 4.8 MEDIUM
  15. 2026-11-18 12:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-132124?
CVE-2026-132124 is a medium-severity vulnerability; its CVE record was published on November 18, 2026. modified eCommerce Shopsoftware through 3.3.0 contains a stored cross-site scripting vulnerability that allows authenticated administrators to inject scripts via the orders_status_name parameter in admin/orders_status.php. Attackers with per-page order status access can store payloads that execute…
When was CVE-2026-132124 made public?
CVE-2026-132124 was made public on November 18, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 18, 2026. EchelonGraph's copy of the record carries a last-modified date of November 21, 2026; the record at its source may have been updated since.
Is CVE-2026-132124 actively exploited?
CVE-2026-132124 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-132124?
CVE-2026-132124 has a CVSS base score of 4.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-132124?
An upstream fix for CVE-2026-132124 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-132124 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-132124

Explore →

Is Your Infrastructure Affected by CVE-2026-132124?

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