VulnerabilityPublished 17 Jun 2025Updated 20 Jun 2025

CVE-2025-30680: Trend Micro Apex Central · SSRF

Affects Trend Micro Apex CentralSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 17 Jun 2025
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

AI-suggested

Verify that the SaaS instance of Trend Micro Apex Central is running the latest monthly maintenance release from Trend Micro, as these updates automatically address the SSRF vulnerability.
Restrict and monitor privileged user accounts within Apex Central to minimize the risk of exploitation by insiders or compromised credentials.
Implement network segmentation and strict egress filtering to limit the ability of the SaaS platform to access internal resources unnecessarily, reducing the impact of SSRF exploitation.
Enable detailed logging and anomaly detection on Apex Central API calls and parameter usage to identify suspicious request patterns indicative of SSRF attempts.
Conduct regular security assessments and penetration testing focused on the SaaS environment to validate that no residual SSRF or related vulnerabilities exist.
Coordinate with Trend Micro support to confirm the SaaS environment’s patch status and receive guidance on any additional configuration hardening.
Educate security teams on SSRF risks specific to SaaS platforms and incorporate SSRF detection into incident response playbooks tailored for cloud-managed security products.

Description

A Server-side Request Forgery (SSRF) vulnerability in Trend Micro Apex Central (SaaS) could allow an attacker to manipulate certain parameters leading to information disclosure on affected installations. Please note: this vulnerability only affects the SaaS instance of Apex Central - customers that automatically apply Trend Micro's monthly maintenance releases to the SaaS instance do not have to take any further action.

Impact

For European organizations using the SaaS version of Trend Micro Apex Central, this vulnerability poses a significant risk of sensitive information disclosure. Given Apex Central’s role in managing security policies and endpoint protection, exposure of internal configuration data or metadata could aid attackers in further reconnaissance or lateral movement within the network. Confidentiality is the primary concern, as attackers could access internal services or data not intended for external access. Although integrity and availability impacts are low or none, the leakage of sensitive security management information could undermine trust in the security posture and facilitate subsequent attacks. European organizations in sectors with stringent data protection requirements (e.g., finance, healthcare, critical infrastructure) could face regulatory and compliance repercussions if sensitive data is exposed. The fact that exploitation requires some level of privileges limits the attack surface but does not eliminate risk, especially if insider threats or compromised accounts exist. The automatic patching of the SaaS platform reduces exposure, but organizations relying on delayed updates or custom configurations may remain vulnerable. Overall, the vulnerability could weaken the security management framework and increase the risk of targeted attacks against European enterprises relying on Trend Micro’s SaaS security management.

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 17 Jun 2025, 20:19 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats