Skip to main content

SveltyCMS EUVDEUVD-2026-82980

| CVE-2026-93506 MEDIUM
Server-Side Request Forgery (SSRF) (CWE-918)
2026-09-18 VulDB GHSA-88rq-v8pm-8jvf
5.3
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privileged user
  2. Delivery
    Submit crafted URL to /mediagallery/upload-media
  3. Exploit
    Server fetches attacker-controlled remote resource
  4. Execution
    Reach internal service or cloud metadata
  5. Impact
    Disclose internal response data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated low-privileged account (CVSS PR:L) on a SveltyCMS 0.0.6 instance and access to the File Upload Endpoint at /mediagallery/upload-media, which fetches an attacker-supplied remote media/importer URL server-side. Exploitation is limited by: the need for valid credentials (not pre-auth), low resulting impact (VC:L/VI:L/VA:L, no scope change), and the requirement that the target be a reachable running SveltyCMS instance with the remote-media fetch feature exercised. No user interaction is needed (UI:N).

Impact

Multi-source signals point to a real-but-modest issue, not a top priority. The vendor (VulDB) CVSS 4.0 base score is 5.3 with vector AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L - network-reachable and low-complexity, but requiring at least low-privileged authentication (PR:L) and yielding only low impact across confidentiality, integrity and availability. There is no EPSS score, no CISA KEV listing, and no public exploit code in the provided intelligence, so exploitation status is: no public exploit identified at time of analysis. The E:X (exploit maturity Not Defined) in the vendor vector reinforces that maturity is unknown rather than proven. This is a classic CWE-918 SSRF in a file-upload/remote-media path, and the low VC/VI/VA and PR:L requirement mean it is a defense-in-depth SSRF rather than a wormable pre-auth RCE. Notable data gap: the provided GitHub commit diff only shows changes to AGENTS.md (security guidance) and bun.lock (dependency bumps) - it does NOT contain the actual endpoint code fix (e.g. validateEgressUrl/safeFetch enforcement on /mediagallery/upload-media), so the precise remediated code path cannot be independently confirmed from the shown hunk. Overall: legitimate to patch, but low real-world urgency given the authentication requirement, low impact, absent exploitation signals, and a very early-stage (0.0.6) niche product.

Exploit ScenarioDerived

A low-privileged authenticated user of a SveltyCMS 0.0.6 instance submits a crafted request to the /mediagallery/upload-media endpoint supplying an attacker-controlled remote media/import URL, causing the server to fetch it. By pointing the URL at internal services, localhost, or cloud metadata endpoints (169.254.169.254), the attacker coerces the server into making outbound requests to otherwise-unreachable internal resources. No public proof-of-concept is provided; the CVSS vector indicates remote, low-complexity exploitation but requires valid low-privileged credentials.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 18, 2026

Server-side request forgery in SveltyCMS 0.0.6 lets an authenticated, low-privileged user (CVSS PR:L, confirmed in both the supplied CVSS 4.0 vector and the independent assessment) force the server to make outbound requests by supplying a crafted remote media/importer URL to the File Upload Endpoint at /mediagallery/upload-media. Exploitation requires valid credentials on a reachable instance that exercises remote media fetching, and the resulting impact is limited (low confidentiality, integrity, and availability, no scope change, no user interaction) - this is a real-but-modest issue rather than a top-priority one. No public exploit code was identified at time of analysis, the flaw is not confirmed actively exploited (CISA KEV), and the vendor has published an upstream fix commit (05b4f9efeb79e9d72a693232334d7529687f896f) that replaces raw outbound fetches with validated egress helpers.

RemediationAI

Upstream fix available (commit 05b4f9efeb79e9d72a693232334d7529687f896f); a released patched version number is not independently confirmed, so treat the commit - or a later tagged release containing it - as the upgrade target (see https://github.com/SveltyCMS/SveltyCMS/commit/05b4f9efeb79e9d72a693232334d7529687f896f). Because the fix is code-level (replace any fetch(userUrl) on remote media/importer URLs with validateEgressUrl plus safeFetch or MediaService.saveRemoteMedia, which reject private IPs, localhost, cloud metadata ranges, DNS rebinding, and redirect hops), applying it requires redeploying the CMS rather than a configuration toggle. If immediate patching is not possible, the most effective compensating control is network egress restriction on the SveltyCMS host: block outbound traffic to RFC1918 ranges, loopback, link-local, and the cloud metadata address 169.254.169.254, allowing only an explicit allowlist of media/CDN destinations - the trade-off is that legitimate third-party remote imports stop working until allowlisted. As a secondary control, disable or gate the remote-media import/upload-media feature so only trusted administrators can supply URLs, and require IMDSv2 or disable instance metadata access entirely on cloud hosts so any residual SSRF cannot harvest credentials; both measures reduce functionality for normal publishing workflows. Finally, since exploitation requires only a low-privileged authenticated account (CVSS PR:L), audit and minimize accounts that can reach /mediagallery/upload-media, and review server-side request logs for requests to internal addresses or the metadata endpoint to detect prior abuse.

Affected VersionsENISA

SveltyCMS 0.0.6

Affected Packages

euvd sveltycms no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The bug is a classic CWE-918 server-side request forgery in the media-upload workflow of SveltyCMS, a Bun/SvelteKit-based headless CMS (the reproducer's dependency lockfile shows Bun tooling, bun:sqlite, AWS SDK S3 media adapters, and Paraglide i18n). The vulnerable component is the remote-media/importer path reached through /mediagallery/upload-media: instead of storing only client-uploaded bytes, the endpoint accepted a user-supplied URL and fetched it server-side without egress validation, allowing the CMS process's network position to be abused. The supplied patch diff makes the intended fix explicit - its security guidance states that code must 'never fetch(userUrl) for remote media or importer URLs' and must instead use validateEgressUrl plus safeFetch or MediaService.saveRemoteMedia, which block private IPs, localhost, cloud metadata endpoints, DNS rebinding, and redirect hops. The same commit bundles adjacent hardening (a fail-closed adapter that strips role/isAdmin/permissions from user attribute updates, and mandatory buffering plus sanitizeSvg for SVG uploads), so the SSRF fix ships alongside broader security-policy changes rather than in isolation. The affected CPE is a wildcard version entry (cpe:2.3:a:n/a:sveltycms:*:*:*:*:*:*:*:*), meaning the public record does not bound a precise version range; the description names 0.0.6, and the independent assessment is consistent with a moderate-severity, authenticated-only SSRF.

Know when Sveltycms gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 5.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
vuln.today AI 5.4 MEDIUM

Network SSRF reachable by a low-privileged authenticated user (PR:L, AC:L, UI:N); primary impact is limited internal-resource disclosure (C:L) with minor integrity (I:L) and no availability or scope change.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

A vulnerability was determined in SveltyCMS 0.0.6. This issue affects some unknown processing of the file /mediagallery/upload-media of the component File Upload Endpoint. Executing a manipulation can lead to server-side request forgery. The attack can be launched remotely. This patch is called 05b4f9efeb79e9d72a693232334d7529687f896f. It is best practice to apply a patch to resolve this issue.

Threat Intelligence Overview

EPSS Score
0.4%
Top 71% exploitable
Prevalence
Rare
very early-stage (v0.0.6) niche open-source SvelteKit CMS, minimal production footprint
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy