CVE-2026-113671 apostrophecms CVE debrief

Who should care

Defenders and administrators of ApostropheCMS installations using @apostrophecms/ai-helper should assess exposure and apply patches to prevent authenticated SSRF attacks. They should prioritize verifying exposure and applying patches, and review compensating controls for exposed systems while remediation is scheduled and verified.

Why it matters

Authenticated SSRF vulnerability in @apostrophecms/ai-helper allows attackers to send unauthorized requests, potentially reaching internal hosts and ports. Defenders should prioritize verifying exposure and applying patches.

• Potential unauthorized access to internal hosts and ports
• Possible data breaches through SSRF
• Increased risk of lateral movement within the network
• Need for verification of @apostrophecms/ai-helper version and patch application

Technical summary

The @apostrophecms/ai-helper package constructs server-side image fetch URLs by resolving storage-relative paths against req.baseUrl. When no global base URL is set, req.baseUrl is derived from the incoming HTTP Host header, allowing an authenticated editor to send unauthorized PATCH requests with attacker-chosen Host headers, enabling SSRF. The vulnerability allows attackers to send unauthorized requests, potentially reaching internal hosts and ports. Defenders should prioritize verifying exposure and applying patches for @apostrophecms/ai-helper versions between 1.0.0-beta.10 and 1.0.0-beta.12.

Defensive priority

Defenders should prioritize verifying exposure and applying patches for @apostrophecms/ai-helper versions between 1.0.0-beta.10 and 1.0.0-beta.12. Authenticated editors could exploit this SSRF vulnerability by sending unauthorized PATCH requests with attacker-chosen Host headers, potentially reaching hosts and ports not otherwise accessible.

Recommended defensive actions

• Verify @apostrophecms/ai-helper version and apply patches if necessary
• Restrict unauthorized PATCH requests to authenticated editors
• Monitor for suspicious outbound GET requests
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Review compensating controls for exposed systems while remediation is scheduled and verified

Evidence notes

The source corpus provides details on the vulnerability in @apostrophecms/ai-helper, including how an authenticated editor can exploit the SSRF vulnerability. However, specific details about affected versions and remediation are limited.

Sources and 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.