{"items":[{"id":"NVI-00012177","kind":"vulnerability","title":"ApostropheCMS: The general public can access @apostrophecms/user objects via a relationship (viewRole is not applied to the general public)","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-xf6w-q65w-4f2w","CVE-2026-113653"],"plain_summary":"GitHub lists this reviewed advisory for apostrophe. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-831ad329154adcfdeacaffe72300c1fc"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.387%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.32848. Missing scores are unknown.","source_id":"sr-831ad329154adcfdeacaffe72300c1fc"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-bd3991838af29a29b62d3d30117acf75","url":"https://github.com/advisories/GHSA-xf6w-q65w-4f2w","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-xf6w-q65w-4f2w","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T23:13:39.183Z"},{"id":"sr-831ad329154adcfdeacaffe72300c1fc","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-113653","publisher":"FIRST EPSS","observed_at":"2026-11-01T01:39:43.067Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-bd3991838af29a29b62d3d30117acf75"],"technology":"apostrophe","known_exclusions":[],"conditions_summary":"### Impact\nEven 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.\n\nThis 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.\n\nThe public demo project and its various flavors must be updated first because it inadvertently relies on the bug.\n\n### Patches\n4.33.0\n\n### Workarounds\nNever 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.","public_affected_ranges":["< 4.33.0"]}],"null_published_at":"2026-11-04T02:53:08.398Z","source_updated_at":"2026-10-20T18:26:03.000Z","source_disclosed_at":"2026-10-20T18:26:02.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T23:13:39.183Z"},{"id":"NVI-00012177","kind":"vulnerability","title":"ApostropheCMS: The general public can access @apostrophecms/user objects via a relationship (viewRole is not applied to the general public)","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-xf6w-q65w-4f2w","CVE-2026-113653"],"plain_summary":"GitHub lists this reviewed advisory for apostrophe. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-bd3991838af29a29b62d3d30117acf75"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-bd3991838af29a29b62d3d30117acf75","url":"https://github.com/advisories/GHSA-xf6w-q65w-4f2w","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-xf6w-q65w-4f2w","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T23:13:39.183Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-bd3991838af29a29b62d3d30117acf75"],"technology":"apostrophe","known_exclusions":[],"conditions_summary":"### Impact\nEven 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.\n\nThis 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.\n\nThe public demo project and its various flavors must be updated first because it inadvertently relies on the bug.\n\n### Patches\n4.33.0\n\n### Workarounds\nNever 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.","public_affected_ranges":["< 4.33.0"]}],"null_published_at":"2026-11-01T01:45:38.494Z","source_updated_at":"2026-10-20T18:26:03.000Z","source_disclosed_at":"2026-10-20T18:26:02.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T23:13:39.183Z"}],"next_cursor":null,"snapshot_revision":"42594"}