VulnerabilityPublished 29 May 2025

CVE-2024-52588: strapi · Server-Side Request Forgery (SSRF)

Affects strapiSource CVE Database V5

Not known to be exploited · CVSS 4.9 Medium : upgrade to 4.25.2 when convenient.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

4.9Medium

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.25.2

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 May 2025
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 26 Oct 2026.

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 strapi/strapi to 4.25.2.

Affected software

Product	Affected	Fixed in
npmstrapi/strapi`pkg:npm/strapi/strapi`Other threats	Affected <4.25.2	Fixed in 4.25.2

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

AI-suggested

1. Upgrade all Strapi instances to version 4.25.2 or later immediately to apply the official patch addressing this SSRF vulnerability. 2. Implement strict input validation and sanitization on Webhooks URL fields to reject local/internal IP addresses and domains, even beyond the patched version, as a defense-in-depth measure. 3. Restrict Strapi server network egress rules to prevent it from making arbitrary HTTP requests to internal services, using firewall rules or network segmentation. 4. Enforce the principle of least privilege for Strapi users, ensuring only trusted administrators have the ability to configure webhooks. 5. Monitor logs for unusual outbound requests initiated by Strapi, especially to internal IP ranges or unexpected domains. 6. Conduct regular security audits and penetration tests focusing on SSRF and related vulnerabilities in webhooks and API integrations. 7. Educate administrators about the risks of SSRF and the importance of cautious webhook configuration.

Description

Strapi is an open-source content management system. Prior to version 4.25.2, inputting a local domain into the Webhooks URL field leads to the application fetching itself, resulting in a server side request forgery (SSRF). This issue has been patched in version 4.25.2.

Impact

For European organizations using Strapi versions prior to 4.25.2, this vulnerability poses a moderate risk. Attackers with authenticated high-level access could exploit SSRF to access internal network resources, potentially exposing sensitive internal APIs, databases, or configuration endpoints. This could lead to unauthorized data disclosure, reconnaissance for further attacks, or pivoting inside the network. Since Strapi is often used in web applications and digital services, exploitation could compromise the confidentiality of business-critical information. The impact is heightened in environments where Strapi is deployed in segmented networks with sensitive internal services. However, the requirement for high privileges limits the attack surface to insiders or compromised accounts. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially in targeted attacks. European organizations in sectors like finance, healthcare, and government, which rely on Strapi for content management and API delivery, should be particularly vigilant due to the sensitivity of their data and regulatory requirements such as GDPR.

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

github.com/strapi/strapi/security/advisories/GHSA-v8wj-f5c7-pvxf (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 04:54 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats