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.
Vulnerability archive 25
Reset filtersdevalue: Residual sparse-array CPU amplification in uneval
devalue: Repeated primitive strings cause quadratic expansion in uneval
devalue: Sparse arrays emitted by uneval cause eager allocation when evaluated
devalue: Custom ArrayBuffer revivers can bypass typed-array allocation validation
devalue: stringifyAsync can cause an unhandled rejection despite a caught returned promise
devalue: Malformed null-prototype object keys bypass __proto__ rejection via property-key coercion
Svelte devalue: DoS via malformed input
xmldom: Quadratic-time attribute deduplication
DOMPurify: SAFE_FOR_TEMPLATES bypass - template expressions survive sanitization inside <template> content when using DOM output modes
qs has a remotely triggerable DoS: qs.stringify crashes with TypeError on null/undefined entries in comma-format arrays when encodeValuesOnly is set
Svelte devalue: DoS via sparse array deserialization
xmldom has XML node injection through unvalidated processing instruction serialization
@stablelib/cbor: Stack exhaustion Denial of Service via deeply nested CBOR arrays, maps, or tags
xmldom: XML injection via unsafe CDATA serialization allows attacker-controlled markup insertion
oRPC has Stored XSS in OpenAPI Reference Plugin via unescaped JSON.stringify
Sveltejs devalue's `devalue.parse` and `devalue.unflatten` emit objects with `__proto__` own properties
devalue has prototype pollution in devalue.parse and devalue.unflatten
devalue affected by CPU and memory amplification from sparse arrays
devalue `uneval`ed code can create objects with polluted prototypes when `eval`ed
devalue vulnerable to denial of service due to memory/CPU exhaustion in devalue.parse
Devalue is vulnerable to denial of service due to memory exhaustion in devalue.parse
Nuxt has Client-Side Path Traversal in Nuxt Island Payload Revival
devalue prototype pollution vulnerability
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.