PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-35569 apostrophecms CVE debrief

ApostropheCMS versions 4.28.0 and prior contain a stored cross-site scripting vulnerability in SEO-related fields. An attacker can inject a payload to break out of the intended HTML context and execute arbitrary JavaScript in the browser of any authenticated user who views the affected page. This vulnerability allows for potential access to sensitive data such as usernames, email addresses, and roles via internal APIs, and can be leveraged to perform authenticated API requests. Defenders should assess exposure and apply the patch to prevent exploitation.

Vendor
apostrophecms
Product
apostrophe
CVSS
HIGH 8.7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-04-15
Original CVE updated
2026-10-26
Advisory published
2026-04-15
Advisory updated
2026-10-26

Who should care

Defenders responsible for ApostropheCMS installations, particularly those with authenticated users who could be affected by the vulnerability, should assess exposure and apply the patch.

Why it matters

Defenders should prioritize verifying exposure and applying the patch to prevent exploitation, as this vulnerability allows an attacker to execute arbitrary JavaScript in the browser of authenticated users.

  • Execution of arbitrary JavaScript in the browser of authenticated users
  • Potential access to sensitive data such as usernames, email addresses, and roles
  • Possible leveraged authenticated API requests

Technical summary

ApostropheCMS versions 4.28.0 and prior contain a stored cross-site scripting vulnerability in SEO-related fields (SEO Title and Meta Description). An attacker can inject a payload to break out of the intended HTML context and execute arbitrary JavaScript in the browser of any authenticated user who views the affected page. This vulnerability allows for potential access to sensitive data such as usernames, email addresses, and roles via internal APIs, and can be leveraged to perform authenticated API requests. The vulnerability has been fixed in version 4.29.0.

Defensive priority

Defenders should prioritize verifying exposure and applying the patch to prevent exploitation.

Recommended defensive actions

  • Verify exposure by checking if the installed version of ApostropheCMS is 4.28.0 or prior.
  • Apply the patch by upgrading to ApostropheCMS version 4.29.0 or later.
  • Monitor for suspicious activity, such as unusual API requests or changes to sensitive data.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. The vulnerability has been fixed in version 4.29.0. Defenders should verify exposure by checking the installed version of ApostropheCMS and apply the patch by upgrading to version 4.29.0 or later. The CVE record and NVD entry also provide additional information on the vulnerability, including its CVSS score and affected versions.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-35569 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-35569

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-35569 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-35569

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.