Skip to main content

Agorum Core CVE-2025-52163

MEDIUM
Server-Side Request Forgery (SSRF) (CWE-918)
2025-07-18 cve@mitre.org
6.5
CVSS 3.1 · Vendor: mitre
Share

Severity by source

Vendor (mitre) PRIMARY
6.5 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
vuln.today AI
6.5 MEDIUM

Network-reachable unauthenticated servlet; S:U retained as direct code execution is absent; I:L included because forged requests can trigger state changes on internal HTTP APIs.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

1
Analysis Generated
Jul 05, 2026 - 02:18 vuln.today

DescriptionCVE.org

A Server-Side Request Forgery (SSRF) in the component TunnelServlet of agorum Software GmbH Agorum core open v11.9.2 & v11.10.1 allows attackers to forcefully initiate connections to arbitrary internal and external resources via a crafted request. This can lead to sensitive data exposure.

AnalysisAI

Server-Side Request Forgery in Agorum core open's TunnelServlet component exposes internal and external network resources to unauthenticated remote attackers through crafted HTTP requests. Affected versions are 11.9.2 and 11.10.1 of the agorum Software GmbH document management platform. No active exploitation is confirmed and the EPSS score sits at the 10th percentile (0.20%), indicating low observed exploitation pressure at time of analysis, though the zero-authentication requirement lowers the barrier for opportunistic scanning.

Technical ContextAI

Agorum core open is a Java-based enterprise content management and document management system. CWE-918 (Server-Side Request Forgery) occurs when an application fetches a remote resource based on user-supplied input without adequate validation or allowlisting of the destination. The TunnelServlet component appears to act as a server-side proxy or relay, accepting a target URL or host parameter from the client and initiating outbound connections on behalf of the server. An attacker exploiting this can coerce the application server into connecting to arbitrary RFC-1918 addresses, localhost services, cloud metadata endpoints (e.g., AWS IMDSv1 at 169.254.169.254), or external attacker-controlled hosts. The CVSS AV:N/PR:N metrics confirm the servlet is reachable over the network without prior authentication, consistent with a publicly exposed servlet endpoint. Affected CPE versions are Agorum core open 11.9.2 and 11.10.1.

Affected ProductsAI

Agorum core open versions 11.9.2 and 11.10.1, developed by agorum Software GmbH, are confirmed affected. The vulnerability is specific to the TunnelServlet component in these releases. The security advisory published by usd HeroLab at https://herolab.usd.de/security-advisories/usd-2025-0025/ is the primary reference for affected version confirmation. No CPE string was provided in the NVD record; affected version ranges beyond 11.9.2 and 11.10.1 are not confirmed from available data.

RemediationAI

Consult the usd HeroLab advisory at https://herolab.usd.de/security-advisories/usd-2025-0025/ for vendor-specific patch guidance, as no explicit fixed version number is available from the current data - the patch status is 'patch available per vendor advisory' but an exact remediated release has not been independently confirmed from the provided sources. As a compensating control, restrict external and internal network access from the Agorum application server using egress firewall rules, permitting only known-good destinations required for legitimate document management operations; this directly limits SSRF reach without disabling TunnelServlet. If TunnelServlet is not required by operational workflows, disable or undeploy the servlet through the application's configuration to eliminate the attack surface entirely - verify business impact before doing so. Additionally, block access to cloud metadata service ranges (169.254.169.254/32, fd00:ec2::254/128) and RFC-1918 address space at the network perimeter if the server is internet-facing. Implement allowlist-based URL validation in any custom integrations that invoke TunnelServlet.

Share

CVE-2025-52163 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy