Free plan, no credit card, first error in minutes.
Create a Project for FreeDiscover which vulnerabilities affect your technologies and how to fix them. Explore clear explanations, affected versions and practical recommendations - from CMS platforms and plugins to application libraries.
ApostropheCMS notification endpoints fail to verify authentication or ownership. An unauthenticated attacker who obtains a valid notification ID can modify or permanently delete another user's notifications.
A vulnerability in ApostropheCMS allows the general public to access user objects through relationships if templates expose them, as viewRole is not enforced for unauthenticated public users.
An authorization bypass in the ApostropheCMS page REST API allows unauthenticated visitors and low-privileged contributors to read restricted page content and site structure metadata.
A substring check in ApostropheCMS import-export tar extraction fails to catch relative directory traversal paths, allowing authenticated users to crash the Node process.
A client-side prototype pollution vulnerability in ApostropheCMS allows attackers to execute arbitrary JavaScript in the context of an authenticated user session if the victim visits a crafted link, potentially leading to unauthorized data access and administrative compromise.
A lack of attempt throttling on ApostropheCMS's authenticated password-change endpoint allows attackers with an active session to repeatedly guess the current password without lockout or rate limiting, potentially enabling account takeover if the password is weak.
In ApostropheCMS before 4.33.0, the exist-in-locale API allows authenticated low-privilege users to determine whether restricted documents and drafts exist and retrieve localized identifiers without proper document-level authorization checks.
A namespace prefix bypass in sanitize-html allows SVG SMIL animation elements to evade URL sink restrictions, potentially enabling cross-site scripting attacks when SVG elements are allowed.
ApostropheCMS uploadfs with the Azure backend and SAS enabled inadvertently exposes container-level SAS tokens in public attachment links. This allows unauthenticated users to read, overwrite, delete, or list blobs stored in the container.
In @apostrophecms/ai-helper, an authenticated editor can supply a crafted Host header to control the server-side image fetch origin, enabling SSRF against internal hosts and ports.
A NoSQL injection vulnerability in the ApostropheCMS import-export module allows authenticated users to match and overwrite unintended documents using crafted update-key values.
An authorization omission in ApostropheCMS allows unauthenticated remote callers knowing a document identifier to verify document existence and retrieve locale publication metadata.
Unauthenticated CSV import requests in ApostropheCMS leave rejected uploaded files in the operating system temporary directory. Remote attackers can exploit this behavior by repeatedly submitting large files, exhausting available disk space and causing a denial of service across host services.
ApostropheCMS packages interpolate user-supplied CAPTCHA tokens without URL encoding into outbound verification requests. Attackers can inject query parameters to cause verification failures and disrupt protected login and form workflows.
Unauthenticated attackers can stream unbounded multipart request bodies to disk via form submission endpoints in ApostropheCMS, leading to disk space exhaustion and a denial-of-service condition.
ApostropheCMS contains a flaw where authenticated users on SQLite or PostgreSQL adapters can delete shared prototype methods via exclusion projections, causing a persistent process-wide denial of service.
ApostropheCMS exposes single-use session migration tokens in URL query parameters, allowing unauthorized clients that obtain the token to take over user sessions and inherit their privileges.
In sanitize-html prior to 2.18.0, an implied close within elements such as <noscript> causes discard regions to end early, allowing raw text content to be erroneously rendered as regular HTML elements.
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.