Cyber Resilience

CVE-2025-12758

Validator Project Validator ≤ 13.15.22

Public PoC
Published
27 November 2025
Modified
14 July 2026
Patch / advisory
View advisory
CVSS Score v4 7.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0051 41th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2025-12758 is a high-severity Incomplete Filtering of One or More Instances of Special Elements (CWE-792) vulnerability in Validator Project Validator. Its CVSS base score is 7.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 41th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-15 (Information Output Filtering) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Versions of the package validator before 13.15.22 are vulnerable to Incomplete Filtering of One or More Instances of Special Elements in the isLength() function that does not take into account Unicode variation selectors (\uFE0F, \uFE0E) appearing in a sequence which…

more

lead to improper string length calculation. This can lead to an application using isLength for input validation accepting strings significantly longer than intended, resulting in issues like data truncation in databases, buffer overflows in other system components, or denial-of-service.

CWE(s)
CWE-792CWE-172

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1027 Obfuscated Files or Information Stealth
Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit.
attack.mitre.org →
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-56200Same product: Validator Project Validator
CVE-2025-27110Shared CWE-172
CVE-2024-48909Shared CWE-172
CVE-2023-25608Shared CWE-792
CVE-2026-42926Shared CWE-172
CVE-2025-47779Shared CWE-792
CVE-2026-48784Shared CWE-172
CVE-2023-20057Shared CWE-792

Affected Assets

validator project
validator
≤ 13.15.22

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

SI-10 directly requires validation of inputs which structurally prevents incomplete special-element filtering from being introduced or exploitable.

SI-15 Information Output Filtering partial match

Output filtering enforces correct encoding or escaping of data leaving the system.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require complete input filtering and validation to prevent this class of weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.28 Secure coding mostly match
degrades

Secure coding explicitly requires correct character encoding and output escaping to avoid CWE-172.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect incomplete filtering but does not itself implement the fix.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and sanitization that directly prevents incomplete filtering of special elements.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for input validation rules that mitigate incomplete special-element filtering.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles encourage defensive input handling but do not prescribe the specific filtering mechanism.

A.8.12 Data leakage prevention none match
none

Data leakage prevention may catch some downstream effects of unfiltered data but does not address the root filtering weakness.

References