How severe is CVE-2025-7783?

No CVSS score has been assigned to CVE-2025-7783 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-7783?

CVE-2025-7783 affects the following packages: form-data (npm), form-data (npm), form-data (npm). Ecosystems affected: npm.

How do I fix CVE-2025-7783?

Update form-data to 2.5.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-7783 is resolved across your whole dependency graph.

How do I detect CVE-2025-7783 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for form-data. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-7783?

O3 pinpoints whether CVE-2025-7783 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2025-7783 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2025-7783, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2025-7783?

CVE-2025-7783 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 75th 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-2025-7783?

CVE-2025-7783 is classified as Insufficient Random Values (CWE-330). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-7783 published, and has it been updated?

CVE-2025-7783 was published on July 18, 2025 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

CVE-2025-7783

form-data uses unsafe random function in form-data for choosing boundary

Also known asGHSA-fjxv-7rqg-78g4

Published

Jul 18, 2025

Updated

Apr 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk75th percentile+0.42%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

form-datanpm

175.2Mdownloads / week

Description

Use of Insufficiently Random Values vulnerability in form-data allows HTTP Parameter Pollution (HPP). This vulnerability is associated with program files lib/form_data.Js.

This issue affects form-data: < 2.5.4, 3.0.0 - 3.0.3, 4.0.0 - 4.0.3.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`form-data`	all versions	2.5.4
📦npm	`form-data`	≥ 3.0.0&&< 3.0.4	3.0.4
📦npm	`form-data`	≥ 4.0.0&&< 4.0.4	4.0.4

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

benweissmann/CVE-2025-7783-poc

POC of CVE-2025-7783

⭐ 32🍴 5Mar 2026

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for form-data. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update form-data to 2.5.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-7783 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-7783 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-7783. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Use of Insufficiently Random Values vulnerability in form-data allows HTTP Parameter Pollution (HPP). This vulnerability is associated with program files lib/form_data.Js. This issue affects form-data: < 2.5.4, 3.0.0 - 3.0.3, 4.0.0 - 4.0.3.

O3 Security · Impact-Aware SCA

Is CVE-2025-7783 in your dependencies?

O3 detects CVE-2025-7783 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works