Understand vulnerabilities.
Protect your applications.
Discover 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.
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.
A denial-of-service vulnerability in Angular Router affects Server-Side Rendering (SSR) on Node.js. Unauthenticated remote attackers can send crafted URLs with empty-path outlet segments to exhaust memory heap or CPU resources, causing worker process crashes and service disruption.
Specially crafted Markdown can trigger quadratic processing time in markdown-it's smartquotes rule when typographer is enabled, potentially causing denial of service.
A double path decoding issue in Hono allows crafted requests to bypass middleware mounted on static prefixes, potentially exposing protected static files to unauthenticated attackers.
An open redirect vulnerability in Angular Server-Side Rendering allows unauthenticated attackers to supply crafted dot-segments that bypass URL checks and redirect users off-origin.
A vulnerability in JupyterLab allows a command link trust prompt to mark a currently active document as trusted instead of the clicked one, potentially allowing buttons in untrusted documents to execute without confirmation.
A vulnerability in aiohttp allows an attacker to keep an idle connection open indefinitely before sending data because the keepalive timeout was not enforced during the initial portion of a request.
A vulnerability in AIOHTTP allowed shared cookies marked with the Secure attribute to potentially be transmitted over unencrypted requests. Upgrading to version 3.14.4 or later resolves this issue.
Multiple issues in aiohttp can cause excessive or unbounded memory usage and high CPU consumption when handling attacker-controlled requests, leading to resource exhaustion.
A missing comma in Mercury's blocklist leaves the /api/terminals endpoint unprotected, allowing unauthenticated network attackers to spawn an interactive OS-level root shell.
Incomplete cpp #include hardening in the Graphify Fortran extractor allows arbitrary host files to be read and exfiltrated into the knowledge graph when indexing an untrusted repository.
An unauthenticated remote code execution vulnerability in Mercury allows network clients to execute arbitrary Python code as the server process user on default deployments due to anonymous access to kernel endpoints.
LoopX serve-status uses an overly permissive CORS policy with wildcard headers on unauthenticated loopback read endpoints. This allows malicious websites visited by the operator to exfiltrate control-plane state and private Markdown files from registered goal repositories without user interaction.
An integer overflow in JavaCV's IP camera frame grabber can cause an infinite loop during buffer expansion when handling untrusted MJPEG HTTP streams. A malicious or modified response header can force the frame-grabbing thread into continuous 100% CPU utilization, resulting in a denial of service.
Know which vulnerabilities affect your application
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.
Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.
A daily digest of new vulnerabilities, critical ones included.
Notifications about important updates.
Practical advice on application security and monitoring.
Type at least two characters to see suggestions.
/opens search↑↓pick a resultEntergo to the resultESCcloses
We respect your privacy
We use cookies to keep the site working and to learn what to improve on it. Without your consent only the essentials run. You can change your choice at any time from the footer.
Read the privacy policy
Cookie settings
Decide what you agree to. Required cookies are always on - without them the site could not even remember this choice.
Read the privacy policy
Always on
Your session, form protection and the memory of this very choice. The site does not work without them, so they cannot be turned off.
Remembering your language, theme and accessibility settings so you do not have to pick them on every visit.
Anonymous visit statistics: which pages get read and where people get lost. This is what we improve the site on.
Measuring how well our ads work and matching them to your interests on external services.