Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-112953 Overview
CVE-2026-112953 is an information disclosure vulnerability in the ApostropheCMS @apostrophecms/import-export module. ApostropheCMS is an open-source Node.js content management system. Versions prior to 3.7.1 generate predictable export archive filenames. An unauthenticated remote requester can download another user's export archive from publicly readable export storage before the archive expires or is removed. Exploitation requires that a user with export permission first create the archive. The issue is fixed in version 3.7.1 of the import-export module. The weakness is categorized under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Critical Impact
Unauthenticated attackers can retrieve exported content, which may include sensitive site data, from publicly readable storage by predicting archive filenames.
Affected Products
- ApostropheCMS @apostrophecms/import-export module versions prior to 3.7.1
- Sites using publicly readable export storage
- Deployments with exports enabled and unauthenticated upload delivery
Discovery Timeline
- 2026-10-20 - CVE-2026-112953 published to NVD
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-112953
Vulnerability Analysis
The import-export module writes export archives to the configured upload storage using filenames that an unauthenticated requester can predict. Because the storage layer serves these objects without authentication in default configurations, any third party who guesses or enumerates a valid filename can download the archive directly over the network. The exposure window lasts from archive creation until the archive expires or is removed by the housekeeping process.
Exploitation does not require authentication to the CMS. It does, however, depend on a legitimate user with export permission triggering an export. The attacker only needs network access to the public asset path. Private upload storage, authenticated upload delivery, or disabling the export feature all remove this exposure path.
Root Cause
The root cause is a deterministic archive naming scheme combined with publicly accessible object storage. Predictable identifiers eliminate the entropy that normally prevents direct object reference attacks on temporary artifacts. The fix in version 3.7.1 introduces unpredictable archive names so that filenames cannot be guessed by external requesters.
Attack Vector
The attack vector is network-based and requires no privileges on the target site. An attacker constructs the expected archive URL based on the known filename pattern and issues an HTTP GET against the public upload path. If the archive exists and has not been removed, the server returns its contents. Because the download bypasses the application's permission checks entirely, the CMS does not log the retrieval as a user-attributable action.
See the GitHub Security Advisory GHSA-5gc8-frw3-3vqm for the maintainer's technical description. The upstream fixes are tracked in commits 06e4b37 and 40b989b, and shipped in the import-export 3.7.1 release.
Detection Methods for CVE-2026-112953
Indicators of Compromise
- Access log entries showing HTTP GET requests to export archive paths from unauthenticated or unfamiliar source addresses.
- Repeated requests enumerating export filenames with sequential or time-based patterns.
- Downloads of archive objects by user agents or IP addresses that do not correlate with any authenticated session on the CMS.
Detection Strategies
- Review upload storage access logs (for example, S3, CloudFront, or NGINX logs) for retrievals of archive files that were not requested through an authenticated CMS session.
- Correlate archive creation events in the CMS with downstream download events and flag downloads lacking a matching authenticated referrer.
- Alert on bursts of 404 responses against the exports path that suggest filename enumeration.
Monitoring Recommendations
- Instrument the exports directory with per-object access telemetry and forward it to a central logging pipeline.
- Track the installed version of @apostrophecms/import-export across environments and alert when versions earlier than 3.7.1 are detected.
- Monitor outbound egress from upload storage buckets for anomalous data volume originating from the exports prefix.
How to Mitigate CVE-2026-112953
Immediate Actions Required
- Upgrade @apostrophecms/import-export to version 3.7.1 or later across all ApostropheCMS deployments.
- Purge any existing export archives from publicly readable storage, since those filenames remain predictable until removed.
- Audit upload storage permissions and remove public read access from the exports path where feasible.
Patch Information
The fix is published in the @apostrophecms/import-export@3.7.1 release. The relevant upstream changes are in GitHub commits 06e4b37 and 40b989b. Review the GitHub Security Advisory GHSA-5gc8-frw3-3vqm for upgrade guidance.
Workarounds
- Disable the import-export feature if it is not required for business operations.
- Move upload storage to a private backend and serve exports through an authenticated delivery endpoint that enforces CMS permissions.
- Shorten the archive retention window so exposed archives are removed quickly after creation.
# Upgrade the import-export module to the fixed version
npm install @apostrophecms/import-export@3.7.1
# Verify the installed version
npm ls @apostrophecms/import-export
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

