CVE-2025-67419
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA Denial of Service (DoS) vulnerability in evershop 2.1.0 and prior allows unauthenticated attackers to exhaust the application server's resources via the "GET /images" API. The application fails to limit the height of the use-element shadow tree or the dimensions of pattern tiles during the processing of SVG files, resulting in unbounded resource consumption and system-wide denial of service.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA Denial of Service vulnerability in evershop 2.1.0 and prior allows unauthenticated attackers to exhaust server resources through the GET /images API by providing maliciously crafted SVG files. The application fails to validate or limit the height of use-element shadow trees or the dimensions of pattern tiles during SVG processing, causing unbounded resource consumption.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Evershop installation and versionLocate the Evershop installation directory and check the package.json file for the version number, or run 'npm list evershop' if Node.js is installedAffected if The installed version is 2.1.0 or any version prior to 2.1.0
-
Verify the /images API endpoint is exposedConfirm the /images endpoint exists and is accessible on the server - check route configuration files in the 'src/routes' or 'routes' directory for any route matching /imagesAffected if The /images endpoint is present and reachable without authentication
-
Confirm SVG file processing is enabled on the endpointTest if the /images endpoint accepts SVG file requests - send a GET request to /images with an SVG file path parameter (e.g., /images/malicious.svg) and verify the server processes and returns the SVG contentAffected if The endpoint accepts and processes SVG files without validation or sanitization
-
Check for absence of SVG resource limitsExamine the codebase for any validation logic that limits SVG element depth, pattern tile dimensions, or overall file size during processing - look for relevant functions in image processing or SVG parsing modulesAffected if No resource limits (element depth, pattern dimensions, file size) are implemented in the SVG processing code
-
Check for rate limiting on the /images endpointReview server configuration or middleware to determine if rate limiting or request timeouts are configured for the /images endpointAffected if No rate limiting or timeout controls are configured for the /images endpoint
The environment is affected if Evershop version 2.1.0 or prior is installed AND the /images endpoint is accessible and processes SVG files without proper resource limits or rate limiting controls.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation and resource limits on SVG file processing, including limits on element depth, pattern tile dimensions, and file size. Add request rate limiting and timeout controls on the /images endpoint to prevent resource exhaustion.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67419 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-67419 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data