A vulnerability was found in MyEMS up to 6.4.0. The affected element is the function on_post of the file myems-api/core/svg.py of the component Admin Backend. The manipulation of the argument new_values['data'] results in cross site scripting. The attack can be launched remotely. The exploit has been made public and could be used. Upgrading to version 6.5.0 is sufficient to fix this issue. The patch is identified as 4a97edfbd786c779d0322054833b21ddf54d5b06. It is suggested to upgrade the affected component. The issue report remains open even though there is an official fix for it.
CVE-2026-15321
Score 2.4 from GitHub Security Advisory (severity: LOW) published 2026-07-10. a secondary CVSS source baseline 2.4; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 2.4
- EG Score
- 2.4(high)
- EPSS
- 12.4%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 10, 2026
References (9)
- cna@vuldbhttps://github.com/MyEMS/myems/
- cna@vuldbhttps://github.com/MyEMS/myems/commit/4a97edfbd786c779d0322054833b21ddf54d5b06
- cna@vuldbhttps://github.com/MyEMS/myems/issues/412
- cna@vuldbhttps://github.com/MyEMS/myems/releases/tag/v6.5.0
- cna@vuldbhttps://vuldb.com/cve/CVE-2026-15321
- cna@vuldbhttps://vuldb.com/submit/853060
- cna@vuldbhttps://vuldb.com/vuln/377263
- cna@vuldbhttps://vuldb.com/vuln/377263/cti
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://vuldb.com/submit/853060
Vendor Advisories for CVE-2026-15321(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 13× in last 7d / 13× 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-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-13 03:25 UTCEG score recompute
- 2026-07-13 03:25 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 20:19 UTCNVD updateCVSS v4 → 1.9
- 2026-07-10 18:57 UTCMITRE cvelistV5CVSS v4 → 4.8
- 2026-07-10 04:54 UTCNVD updateCVSS v4 → 1.9
- 2026-07-10 03:50 UTCEG score recompute
- 2026-07-10 03:48 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-15321?
When was CVE-2026-15321 disclosed?
Is CVE-2026-15321 actively exploited?
What is the CVSS score of CVE-2026-15321?
How do I remediate CVE-2026-15321?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15321
Is Your Infrastructure Affected by CVE-2026-15321?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.