Apostrophecms Apostrophe vulnerabilities
7 known vulnerabilities affecting apostrophecms/apostrophe.
Total CVEs
7
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
HIGH2MEDIUM4LOW1
Vulnerabilities
Page 1 of 1
CVE-2026-35569HIGHCVSS 8.7fixed in 4.29.02026-04-15
CVE-2026-35569 [HIGH] CWE-79 CVE-2026-35569: ApostropheCMS is an open-source Node.js content management system. Versions 4.28.0 and prior contain
ApostropheCMS is an open-source Node.js content management system. Versions 4.28.0 and prior contain a stored cross-site scripting vulnerability in SEO-related fields (SEO Title and Meta Description), where user-controlled input is rendered without proper output encoding into HTML contexts including tags, attributes, and JSON-LD structured data. An att
cvelistv5ghsanvd
CVE-2026-33889MEDIUMCVSS 5.4fixed in 4.29.02026-04-15
CVE-2026-33889 [MEDIUM] CWE-79 CVE-2026-33889: ApostropheCMS is an open-source Node.js content management system. Versions 4.28.0 and prior contain
ApostropheCMS is an open-source Node.js content management system. Versions 4.28.0 and prior contain a stored cross-site scripting vulnerability in the @apostrophecms/color-field module, where color values prefixed with -- bypass TinyColor validation intended for CSS custom properties, and the launder.string() call performs only type coercion without
cvelistv5ghsanvd
CVE-2026-40186MEDIUMCVSS 6.1v>= 4.28.0, < 4.29.02026-04-15
CVE-2026-40186 [MEDIUM] CWE-79 CVE-2026-40186: ApostropheCMS is an open-source Node.js content management system. A regression introduced in commit
ApostropheCMS is an open-source Node.js content management system. A regression introduced in commit 49d0bb7, included in versions 2.17.1 of the ApostropheCMS-maintained sanitize-html package bypasses allowedTags enforcement for text inside nonTextTagsArray elements (textarea and option). ApostropheCMS version 4.28.0 is affected through its dependenc
cvelistv5nvd
CVE-2026-33888MEDIUMCVSS 5.3fixed in 4.29.02026-04-15
CVE-2026-33888 [MEDIUM] CWE-200 CVE-2026-33888: ApostropheCMS is an open-source Node.js content management system. Versions 4.28.0 and prior contain
ApostropheCMS is an open-source Node.js content management system. Versions 4.28.0 and prior contain an authorization bypass vulnerability in the getRestQuery method of the @apostrophecms/piece-type module, where the method checks whether a MongoDB projection has already been set before applying the admin-configured publicApiProjection. An unauthent
cvelistv5ghsanvd
CVE-2026-39857MEDIUMCVSS 5.3fixed in 4.29.02026-04-15
CVE-2026-39857 [MEDIUM] CWE-200 CVE-2026-39857: ApostropheCMS is an open-source Node.js content management system. Versions 4.28.0 and prior contain
ApostropheCMS is an open-source Node.js content management system. Versions 4.28.0 and prior contain an authorization bypass vulnerability in the choices and counts query parameters of the REST API, where these query builders execute MongoDB distinct() operations that bypass the publicApiProjection restrictions intended to limit which fields are exp
cvelistv5ghsanvd
CVE-2026-33877LOWCVSS 3.7fixed in 4.29.02026-04-15
CVE-2026-33877 [LOW] CWE-208 CVE-2026-33877: ApostropheCMS is an open-source Node.js content management system. Versions 4.28.0 and prior contain
ApostropheCMS is an open-source Node.js content management system. Versions 4.28.0 and prior contain a timing side-channel vulnerability in the password reset endpoint (/api/v1/@apostrophecms/login/reset-request) that allows unauthenticated username and email enumeration. When a user is not found, the handler returns after a fixed 2-second artificial d
cvelistv5ghsanvd
CVE-2026-32730HIGHCVSS 8.1fixed in 4.28.02026-03-18
CVE-2026-32730 [HIGH] CWE-287 CVE-2026-32730: ApostropheCMS is an open-source content management framework. Prior to version 4.28.0, the bearer to
ApostropheCMS is an open-source content management framework. Prior to version 4.28.0, the bearer token authentication middleware in `@apostrophecms/express/index.js` (lines 386-389) contains an incorrect MongoDB query that allows incomplete login tokens — where the password was verified but TOTP/MFA requirements were NOT — to be used as fully authent
cvelistv5ghsanvdosv