Skip to main content
CVE-2024-36572VulnerabilityPublished Updated

CVE-2024-36572: form-manager · n/a

Affects form-managerSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% 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:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jul 2024

  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-26.

What to do

Affected software

ProductAffectedFixed in
npmallpro/form-managerpkg:npm/allpro/form-managerOther threatsAffected
  • =0.7.4
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-36572, organizations should immediately identify and inventory all instances of allpro form-manager version 0.7.4 in their environments. 2) Implement runtime protections such as JavaScript sandboxing or object freezing to prevent prototype modifications. 3) Use security tools that detect prototype pollution attempts and anomalous object behavior. 4) If feasible, upgrade to a later, patched version of the library once available or replace the library with a secure alternative. 5) Monitor logs and network traffic for unusual activity related to the vulnerable functions setDefaults, mergeBranch, and Object.setObjectValue. 6) Employ Web Application Firewalls (WAFs) with custom rules to block known attack patterns targeting prototype pollution. 7) Educate development teams about secure coding practices to avoid introducing similar vulnerabilities. These targeted mitigations go beyond generic advice by focusing on the specific functions and attack vectors involved in this vulnerability.

Description

Prototype pollution in allpro form-manager 0.7.4 allows attackers to run arbitrary code and cause other impacts via the functions setDefaults, mergeBranch, and Object.setObjectValue.

References

Community reviews

Loading reviews…