VulnerabilityPublished 11 Oct 2024Updated 15 Oct 2024

CVE-2024-46468: jpress · Server-Side Request Forgery (SSRF)

Affects jpressSource 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 34% 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 11 Oct 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
GitHubjpressprojects/jpress`pkg:github/jpressprojects/jpress`Other threats	Affected <=5.1.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

Apply patches or updates from the jpress development team as soon as they become available to address CVE-2024-46468 directly.
Until patches are released, restrict outbound HTTP requests from the jpress server to only trusted domains using network-level controls such as firewall rules or egress filtering.
Implement input validation and sanitization on any user-supplied URLs or parameters that trigger server-side requests to prevent manipulation.
Use web application firewalls (WAFs) to detect and block suspicious SSRF attack patterns targeting jpress endpoints.
Monitor server logs and network traffic for unusual outbound requests, especially to internal IP ranges or metadata service URLs.
Segment internal networks to limit the exposure of sensitive services that could be accessed via SSRF.
Review and harden cloud metadata service access policies if jpress is deployed in cloud environments to prevent SSRF-based credential theft.
Conduct security assessments and penetration testing focused on SSRF vectors in jpress deployments to identify and remediate weaknesses proactively.

Description

A Server-Side Request Forgery (SSRF) vulnerability exists in the jpress <= v5.1.1, which can be exploited by an attacker to obtain sensitive information, resulting in an information disclosure.

Impact

The primary impact of CVE-2024-46468 is unauthorized information disclosure, which can compromise the confidentiality of sensitive internal data. Organizations running vulnerable jpress versions risk exposing internal services, configuration data, or cloud metadata endpoints that could reveal credentials or infrastructure details. This exposure can facilitate further attacks such as privilege escalation, lateral movement, or data exfiltration. Since the vulnerability requires no authentication and no user interaction, it can be exploited remotely by attackers scanning for vulnerable instances. The scope includes any organization using jpress <= 5.1.1, especially those with sensitive internal networks accessible from the web server. The lack of integrity or availability impact means the vulnerability does not directly allow data modification or service disruption, but the information gained can indirectly lead to more severe compromises. The absence of known exploits in the wild reduces immediate risk but does not eliminate it, as attackers may develop exploits rapidly once details are public. Overall, the threat is significant for organizations relying on jpress for web content management, particularly those with sensitive internal resources behind the web server.

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, 08:37 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats