VulnerabilityPublished 19 Dec 2024Updated 2 Jan 2025

CVE-2024-55082: Stirling-PDF · Server-Side Request Forgery (SSRF)

Affects Stirling-PDFSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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 19 Dec 2024
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 or the CVSS exploit maturity 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

Affected software

Product	Affected	Fixed in
GitHubsummerxxoo/Stirling-PDF`pkg:github/summerxxoo/Stirling-PDF`Other threats	Affected =0.35.1	Fixed in–

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

AI-suggested

Immediately restrict access to the /url-to-pdf endpoint by implementing network-level controls such as IP whitelisting or VPN requirements to limit exposure to trusted users only.
Employ web application firewalls (WAFs) with custom rules to detect and block suspicious SSRF patterns, such as requests containing internal IP ranges or localhost references.
Implement strict input validation and sanitization on the URL parameter to ensure only allowed domains or protocols are accepted, using allowlists rather than blocklists.
Monitor server logs for unusual outbound HTTP requests initiated by the /url-to-pdf endpoint, focusing on internal IP addresses or unexpected destinations.
If possible, isolate the PDF generation service in a segmented network zone with minimal access to sensitive internal resources.
Stay updated with Stirling-PDF vendor announcements and apply patches promptly once available.
Conduct internal security assessments to identify any sensitive services that could be targeted via SSRF and harden them accordingly.
Consider implementing outbound request proxying with strict controls to prevent arbitrary external or internal requests. These measures collectively reduce the attack surface and limit the potential impact until a permanent fix is released.

Description

A Server-Side Request Forgery (SSRF) in the endpoint http://{your-server}/url-to-pdf of Stirling-PDF 0.35.1 allows attackers to access sensitive information via a crafted request.

Impact

The primary impact of CVE-2024-55082 is the unauthorized disclosure of sensitive information within an organization's internal network or from protected external resources. Attackers exploiting this SSRF vulnerability can bypass network segmentation and firewall rules, accessing internal services that are not exposed to the internet. This can lead to leakage of confidential data, such as internal APIs, metadata services, or administrative interfaces. While the vulnerability does not directly affect data integrity or system availability, the information gained can facilitate subsequent attacks, including privilege escalation or lateral movement. Organizations relying on Stirling-PDF for PDF generation in web applications or automated workflows are at risk, especially if the vulnerable endpoint is exposed to untrusted users or the internet. The absence of authentication requirements and user interaction increases the likelihood of exploitation. The lack of patches means organizations must rely on mitigations until an official fix is available. Overall, this vulnerability poses a significant risk to confidentiality and could be a stepping stone for more severe attacks.

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 26 Feb 2026, 02:02 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats