CVE-2025-36845VulnerabilityPublished 21 Jul 2025

CVE-2025-36845: n/a

Source CVE Database V5

Not known to be exploited · public detection template (Nuclei) · CVSS 8.6 High.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

8.6High

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

EPSS: 1.7% chance of exploitation in 30 days – higher than 77% 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:C/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
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: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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 21 Jul 2025
Detectable: evidence found.
nuclei template: Eveo URVE Web Manager - Server-Side Request Forgery
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 2026-10-26.

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

AI-suggested

European organizations should immediately audit their deployment of Eveo URVE Web Manager to determine if they are running the affected version 27.02.2025. Until a patch is available, organizations should implement network-level controls to restrict the application server’s ability to make arbitrary outbound HTTP requests, such as firewall rules or egress filtering that limit requests to trusted destinations only. Web application firewalls (WAFs) can be configured to detect and block suspicious requests targeting the /_internal/redirect.php endpoint, especially those containing external or internal IP addresses or URLs. Application-level mitigations include disabling or restricting the functionality of the vulnerable endpoint if feasible, or implementing strict input validation and allowlisting of URLs that the redirect.php endpoint can access. Monitoring and logging of requests to this endpoint should be enhanced to detect potential exploitation attempts. Organizations should also prepare to deploy patches promptly once Eveo releases a fix. Finally, internal network segmentation and zero-trust principles should be reinforced to minimize the impact of any SSRF exploitation.

Description

An issue was discovered in Eveo URVE Web Manager 27.02.2025. The endpoint /_internal/redirect.php allows for Server-Side Request Forgery (SSRF). The endpoint takes a URL as input, sends a request to this address, and reflects the content in the response. This can be used to request endpoints only reachable by the application server.

Impact

For European organizations using Eveo URVE Web Manager, this SSRF vulnerability poses a significant risk to internal network security and data confidentiality. Organizations often deploy such management platforms within their internal networks or DMZs, where they have access to sensitive infrastructure components such as databases, internal APIs, or cloud metadata services. Exploitation could allow attackers to pivot from the exposed web application into internal systems, potentially leading to unauthorized data access, lateral movement, or disruption of critical services. Given the reflective nature of the vulnerability, attackers could also use it to exfiltrate data or perform reconnaissance on internal network topology. The impact is heightened in sectors with stringent data protection requirements, such as finance, healthcare, and critical infrastructure, common across Europe. Additionally, the lack of authentication requirements means that attackers can exploit this vulnerability remotely without valid credentials, increasing the attack surface. The absence of a patch or mitigation guidance further elevates the risk until a fix is released and applied.

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

Description

AI analysisMachine-generated, updated 21 Jul 2025, 18:16 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats