sassdoc-extras vulnerable to prototype pollution

published 2025-09-24 last yr. modified 2026-06-17 4mo ago also GHSA-3mpm-jx38-9m8w , EUVD-2025-31057

cvss: 7.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 36%
public exploits: 0; none known

A Prototype Pollution vulnerability in the byGroupAndType function of sassdoc-extras v2.5.1 and before allows attackers to inject properties on Object.prototype via supplying a crafted payload, causing denial of service (DoS) as the minimum consequence.

Is CVE-2025-57326 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: last yr. (2025-09-26)

Exploit prediction

0.41% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem	package	affected	fixed in
npm	sassdoc-extras	<=3.0.0	no fix listed

Classification

Weakness

CWE-1321 Improperly Controlled Modification of Object Prototype Attributes

References

github.com /VulnSageAgent/PoCs/blob/main/JavaScript/prototype-pollution/sassdoc-extras%402.5.1/index.js
web, broken-link
github.com /VulnSageAgent/PoCs/tree/main/JavaScript/prototype-pollution/CVE-2025-57326
web, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2025-57326
advisory
github.com /SassDoc/sassdoc-extras
package

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.