CVE-2024-51980

What it is

An unauthenticated attacker may perform a limited server side request forgery (SSRF), forcing the target device to open a TCP connection to an arbitrary port number on an arbitrary IP address. This SSRF leverages the WS-Addressing ReplyTo element in a Web service (HTTP TCP port 80) SOAP request. The attacker can not control the data sent in the SSRF connection, nor can the attacker receive any data back. This SSRF is suitable for TCP port scanning of an internal network when the Web service (HTTP TCP port 80) is exposed across a network segment.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

1.0% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2025-06-25 08:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 08:06 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.0% in the next 30 days (EPSS).
• Severity: 5.3 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2025-06-25 08:15 UTC

Last modified

2026-06-17 08:06 UTC

Exploit probability

1.0% · EPSS, next 30 days

Weakness

CWE-918 · Server-side request forgery

Record status

Deferred

Attack profile CVSS 3.1 · 5.3

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2024-51980.md and follow it. Check whether this project is affected by CVE-2024-51980. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge