CVE-2026-25493VulnerabilityPublished 9 Feb 2026

CVE-2026-25493: craftcms cms · Server-Side Request Forgery (SSRF)

Affects craftcms cmsSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium : upgrade to 5.8.22 or 4.16.18 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.8.22, 4.16.18

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade craftcms cms to 5.8.22 or 4.16.18.

Affected software

Product	Affected	Fixed in
craftcmscms	Affected >=5.0.0-RC1 <5.8.22 >=4.0.0-RC1 <4.16.18	Fixed in 5.8.22 4.16.18

AI-suggested

1. Upgrade Craft CMS to version 4.16.18 or later, or 5.8.22 or later, which contain patches addressing this SSRF vulnerability. 2. If immediate upgrade is not feasible, implement network-level controls to restrict outbound HTTP requests from the Craft CMS server to internal IP ranges and cloud metadata IP addresses (e.g., 169.254.169.254 for AWS). 3. Review and harden GraphQL endpoint access controls to limit exposure to trusted users or IP addresses. 4. Monitor logs for unusual outbound HTTP requests or redirects originating from the Craft CMS server. 5. Employ web application firewalls (WAFs) with rules to detect and block SSRF patterns or suspicious redirect chains. 6. Conduct internal penetration testing focusing on SSRF vectors to identify similar weaknesses. 7. Educate developers and administrators about SSRF risks and secure coding practices related to URL validation and HTTP client usage. These steps go beyond generic advice by combining patching with network segmentation, monitoring, and access control enhancements tailored to the specific vulnerability mechanism.

Description

CVE-2026-25493 is a Server-Side Request Forgery (SSRF) vulnerability in Craft CMS versions 4.0.0-RC1 through 4.16.17 and 5.0.0-RC1 through 5.8.21. The vulnerability arises because the saveAsset GraphQL mutation attempts to block SSRF by validating the initial URL hostname and resolved IP against a blocklist, but the underlying HTTP client (Guzzle) follows redirects by default.

Impact

For European organizations, this SSRF vulnerability poses a risk of unauthorized internal network access and exposure of sensitive internal resources, such as cloud metadata endpoints or internal APIs. Attackers exploiting this flaw could gather confidential information about the infrastructure, credentials, or configuration data, which could facilitate further attacks like privilege escalation or lateral movement. Organizations using Craft CMS in cloud environments (e.g., AWS, Azure, GCP) are particularly at risk because cloud metadata services often contain sensitive data like instance credentials and configuration. This could lead to data breaches, compliance violations (e.g., GDPR), and reputational damage. The vulnerability's exploitation does not require authentication or user interaction, increasing the likelihood of automated attacks. However, the impact is somewhat limited by the need for the target to be running a vulnerable Craft CMS version and the attacker’s ability to control or induce redirects. Overall, the threat is significant for organizations relying on Craft CMS for public-facing or internal digital experiences, especially those with sensitive internal network segments or cloud infrastructure.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Feb 2026, 09:44 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats