Security Resilience

CVE-2024-13904

SSRF in Platformly Platform.Ly For Woocommerce ≤ 1.1.7

Published
07 March 2025
Modified
13 March 2025
Patch / advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0042 35th percentile
Risk Priority 45 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-13904 is a medium-severity SSRF (CWE-918) vulnerability in Platformly Platform.Ly For Woocommerce. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique LSASS Memory (T1003.001); ranked at the 35th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-13904 is a Blind Server-Side Request Forgery (SSRF) vulnerability, mapped to CWE-918, affecting the Platform.ly for WooCommerce plugin for WordPress in all versions up to and including 1.1.6. The flaw exists in the 'hooks' function, which allows unauthenticated attackers to make web requests to arbitrary locations originating from the web application. It has a CVSS v3.1 base score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) and was published on 2025-03-07.

Unauthenticated attackers can exploit this vulnerability remotely with low attack complexity and no user interaction or privileges required. Exploitation enables attackers to leverage the web server to query and modify information from internal services that are not directly accessible from the internet, potentially leading to data leakage or unauthorized internal interactions.

References indicate mitigation through patching. The vulnerable code is visible in the plugin source at platformly-for-woocommerce.php line 167 on the WordPress plugin trac, with a fix applied in changeset 3249460. Wordfence provides further threat intelligence details on the vulnerability.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The Platform.ly for WooCommerce plugin for WordPress is vulnerable to Blind Server-Side Request Forgery in all versions up to, and including, 1.1.6 via the 'hooks' function. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations…

more

originating from the web application and can be used to query and modify information from internal services.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1003.001 LSASS Memory Credential Access
Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
T1021.001 Remote Desktop Protocol Lateral Movement
Adversaries may use [Valid Accounts](https://attack.
T1021.002 SMB/Windows Admin Shares Lateral Movement
Adversaries may use [Valid Accounts](https://attack.
T1021.004 SSH Lateral Movement
Adversaries may use [Valid Accounts](https://attack.
T1021.007 Cloud Services Lateral Movement
Adversaries may log into accessible cloud services within a compromised environment using [Valid Accounts](https://attack.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-32718Same product class: WordPress / CMS plugin
CVE-2025-6729Same product class: WordPress / CMS plugin
CVE-2024-22134Same product class: WordPress / CMS plugin
CVE-2024-13923Same product class: WordPress / CMS plugin
CVE-2024-4469Same product class: WordPress / CMS plugin
CVE-2024-6584Same product class: WordPress / CMS plugin
CVE-2024-38730Same product class: WordPress / CMS plugin
CVE-2025-26990Same product class: WordPress / CMS plugin
CVE-2025-5817Same product class: WordPress / CMS plugin
CVE-2023-51676Same product class: WordPress / CMS plugin

Affected Assets

platformly
platform.ly for woocommerce
≤ 1.1.7

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.6
  • V1.5.3
  • V5.3.2
  • V10.4.7

Mitigating Controls (NIST 800-53 r5) AI

Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.

Input validation directly stops untrusted URLs from being accepted and fetched without destination checks.

Boundary protection limits the network reach of server-initiated requests even if SSRF occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

DE.CM-09 partial match
blocks

Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.

ID.RA-01 partial match
blocks

Vulnerability identification processes can discover and record SSRF flaws in web applications.

PR.IR-01 partial match
blocks

Network segmentation and egress controls can limit the damage from successful SSRF requests.

PR.PS-06 partial match
blocks

Secure development practices directly include input validation and destination allow-listing that prevent SSRF.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

removes
removes
removes
removes

References