CVE-2026-112952: ApostropheCMS Information Disclosure via Slug Enumeration

apostrophe Updated 21 Oct 2026

Summary

21/10/2026
Yes i
Moderate
4.3

CVE-2026-112952: The slugTaken endpoint returns a boolean indicating whether a slug is in use across all document types and visibility levels, with no permission or type filter. Affects apostrophe versions < 4.34.0. Fixed in 4.34.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

ApostropheCMS is an open-source content management system (CMS) designed for building websites and applications with a focus on ease of use and flexibility. It allows users to create, manage, and publish content seamlessly. However, a vulnerability exists in the slugTaken API endpoint, which can expose private and admin-only content to authenticated users, undermining the security of the CMS.

Vulnerability Detail

The vulnerability arises from the slugTaken endpoint in ApostropheCMS, which allows any authenticated user to check if a slug is in use without proper permission checks. This endpoint returns a boolean indicating the existence of a slug across all document types and visibility levels, including private pages, drafts, and archived content. As a result, an attacker can enumerate slugs and gain insights into the full content inventory of the CMS, including sensitive information they should not have access to.

How To Fix

Latest published version: 4.34.0 as of 23 Oct 2026

npm install apostrophe@4.34.0

The newest release already contains this fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, you can restrict access to the slugTaken endpoint by implementing custom middleware that checks user permissions before allowing access to this API. However, this is not a permanent solution and updating the package is recommended.

Conclusion

The ApostropheCMS vulnerability CVE-2026-112952 poses a significant risk by allowing authenticated users to enumerate private content through the slugTaken endpoint. It is crucial to update to the patched version 4.34.0 or later to mitigate this risk and protect sensitive information.

See every vulnerability recorded for apostrophe →

Share this vulnerability

FAQ

The CVSS score of this vulnerability is 4.3, indicating a moderate severity level.

Any authenticated user with access to the ApostropheCMS can exploit this vulnerability, including editors and contributors.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If you cannot update the package right away, implement custom middleware to restrict access to the slugTaken endpoint as a temporary measure.

The impact includes information disclosure, allowing attackers to enumerate slugs and potentially access sensitive content that should be restricted.

Related vulnerabilities

Recent vulnerabilities recorded for apostrophe.

How To Fix

Latest published version: 4.34.0 as of 23 Oct 2026

npm install apostrophe@4.34.0

The newest release already contains this fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback