Skip to main content
CVE-2025-57320VulnerabilityPublished Updated

CVE-2025-57320: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

AI-suggested

1. Immediate mitigation involves auditing the use of json-schema-editor-visual in all applications and development environments to identify affected versions (up to 1.1.1). 2. Since no official patches are currently linked, organizations should monitor the package repository and security advisories for updates or patches addressing this vulnerability and apply them promptly once available. 3. As a temporary measure, consider implementing input validation and sanitization to prevent malicious payloads from reaching the vulnerable functions. 4. Employ runtime application self-protection (RASP) or web application firewalls (WAFs) that can detect and block suspicious payloads targeting prototype pollution. 5. Conduct code reviews and static analysis to detect unsafe usage of Object.prototype manipulation in custom code. 6. Educate developers about prototype pollution risks and secure coding practices to prevent similar vulnerabilities. 7. For critical systems, consider isolating or sandboxing components that use this package to limit the blast radius of potential attacks.

Description

json-schema-editor-visual is a package that provides jsonschema editor. A Prototype Pollution vulnerability in the setData and deleteData function of json-schema-editor-visual versions thru 1.1.1 allows attackers to inject or delete properties on Object.prototype via supplying a crafted payload, causing denial of service (DoS) as the minimum consequence.

References

Community reviews

Loading reviews…