How severe is CVE-2013-7453?

CVE-2013-7453 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2013-7453?

CVE-2013-7453 affects the following packages: validator (npm). Ecosystems affected: npm.

How do I fix CVE-2013-7453?

Update validator to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-7453 is resolved across your whole dependency graph.

How do I detect CVE-2013-7453 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for validator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-7453 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2013-7453 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-7453 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-7453?

CVE-2013-7453 has an EPSS (Exploit Prediction Scoring System) score of 1.9%, placing it in the 78th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-7453?

CVE-2013-7453 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2013-7453 published, and has it been updated?

CVE-2013-7453 was published on October 24, 2017 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

MEDIUM severity

CVE-2013-7453 — validator

MEDIUM

CVE-2013-7453 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in validator. A fix is available for validator — see the affected versions and patch details below.

Moderate severity vulnerability that affects validator

Published

Oct 24, 2017

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

7Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

validatornpm

28.9Mdownloads / week

Description

The validator module before 1.1.0 for Node.js allows remote attackers to bypass the cross-site scripting (XSS) filter via vectors related to UI redressing.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`validator`	all versions	1.1.0`npm install validator@1.1.0`

Affected Products

1 product · 1 configurations

Application

node.jsnodejs

≤ 1.0.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for validator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update validator to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-7453 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

The validator module before 1.1.0 for Node.js allows remote attackers to bypass the cross-site scripting (XSS) filter via vectors related to UI redressing.

O3 Security · Impact-Aware SCA

Is CVE-2013-7453 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Oct 24, 2017

Last updated

Nov 8, 2023

Identifiers

CVE-2013-7453

References

Advisorynvd.nist.gov · CVE 2013 7453 Advisorygithub.com · GHSA 552w rqg8 gxxm Webopenwall.com

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting validator are rated as high or higher (top: high).

CVE-2025-12758CVE-2025-56200GHSA-xx4c-jj58-r7x6CVE-2021-3765CVE-2014-8882CVE-2014-9772CVE-2013-7454CVE-2013-7451

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedNov 8, 2023