Live › vulnerability › CVE-2026-113653
Go to dashboardApostropheCMS does not apply the viewRole permission to the general public, so anonymous visitors can read @apostrophecms/user documents through a relationship field. An attacker can see user record data exposed by a blog post or similar template, such as names or emails if the template serializes the whole user object; password hashes are stored separately and not exposed.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 3h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| apostrophe | npm | < 4.33.0 | 4.33.0 |
npm ls apostrophe4.33.0 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Even though it is correctly applied to guests, contributors, etc., viewRole is not applied to the general public. This means that a secured content type like @apostrophecms/user can in theory be accessed.
This is greatly mitigated by the fact that there is no automatic public REST API for any content type. One has to expressly allow it. However, it does mean that developers can make the mistake of setting up a relationship between a content type like a blog post, and @apostrophecms/user. This could potentially expose some sensitive information if templates were written poorly, e.g. if they JSON-serialized the entire object. Note that password hashes are NOT affected because they reside in a separate collection.
The public demo project and its various flavors must be updated first because it inadvertently relies on the bug.
4.33.0
Never create relationships with @apostrophecms/user that are intended for non-admin display. If you need a relationship that expresses authorship, create a separate author piece type to publicly represent that.
This page as .md · .json · in your agent: get_signal("CVE-2026-113653")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.