Skip to main content
VulnerabilityPublished Updated

CVE-2024-36577: js-object-resolver · Cross-site Scripting

Affects js-object-resolverSource CVE Database V5

0

Not known to be exploited · CVSS 8.3 High : upgrade to 3.1.1 soon.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.1.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Jun 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 26 Oct 2026.

What to do

Upgrade apphp/js-object-resolver to 3.1.1.

Affected software

ProductAffectedFixed in
npmapphp/js-object-resolverpkg:npm/apphp/js-object-resolverOther threatsAffected
  • <3.1.1
Fixed in
  • 3.1.1

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-36577, organizations should promptly upgrade the apphp js-object-resolver library to version 3.1.1 or later once it is available, as this version addresses the Prototype Pollution vulnerability. In the interim, developers should implement strict input validation and sanitization to prevent untrusted data from influencing nested property assignments in the Module.setNestedProperty function. Employing security-focused code reviews and static analysis tools can help identify and remediate unsafe prototype manipulations. Additionally, applying runtime protections such as Content Security Policy (CSP) and enabling JavaScript engine hardening features can reduce exploitation impact. Monitoring application logs for unusual behavior related to object prototype modifications is advisable. Organizations should also maintain an inventory of applications using this library to prioritize patching efforts. Finally, educating developers about Prototype Pollution risks and secure coding practices will help prevent similar vulnerabilities.

Description

apphp js-object-resolver < 3.1.1 is vulnerable to Prototype Pollution via Module.setNestedProperty.

References

Community reviews

Loading reviews…