Skip to main content
VulnerabilityPublished Updated

CVE-2026-93506: SveltyCMS · Server-Side Request Forgery

Affects SveltyCMSSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 2 Nov 2026, 22:58 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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/E:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
SveltyCMSAffected
  • =0.0.6
Fixed in–
GitHubsveltycms/SveltyCMSpkg:github/sveltycms/SveltyCMSOther threatsAffected
  • =0.0.6
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:sveltycms:sveltycms:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch identified by commit 05b4f9efeb79e9d72a693232334d7529687f896f is available and should be applied to resolve this vulnerability. Applying this official fix is the recommended remediation. No other mitigation or temporary workaround is indicated.

Description

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.

References

Community reviews

Loading reviews…