CVE-2025-30679VulnerabilityPublished 17 Jun 2025Updated 20 Jun 2025

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

Affects Trend Micro Apex CentralSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.5Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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 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 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

Affected software

Product	Affected	Fixed in
Trend Micro, Inc. Trend Micro Apex Central	Affected =8.0	Fixed in–

AI-suggested

1. Immediate mitigation should include restricting network access to the Apex Central server, especially limiting inbound traffic to trusted sources only, to reduce exposure to remote attackers. 2. Implement strict input validation and parameter sanitization on the modOSCE component to prevent manipulation of request parameters. 3. Monitor network traffic and logs for unusual outbound requests originating from the Apex Central server that could indicate SSRF exploitation attempts. 4. Employ web application firewalls (WAFs) with rules tailored to detect and block SSRF patterns targeting the Apex Central interfaces. 5. Educate users and administrators about phishing and social engineering risks, as user interaction is required for exploitation. 6. Coordinate with Trend Micro for timely patches or updates and prioritize their deployment once available. 7. Conduct internal security assessments and penetration testing focusing on SSRF vectors within Apex Central deployments. 8. Segment the network to isolate the Apex Central server from sensitive internal resources, minimizing the impact of any SSRF exploitation. 9. Review and harden the configuration of Apex Central, disabling unnecessary services or components that could be leveraged in SSRF attacks.

Description

A Server-side Request Forgery (SSRF) vulnerability in Trend Micro Apex Central (on-premise) modOSCE component could allow an attacker to manipulate certain parameters leading to information disclosure on affected installations.

Impact

For European organizations, the impact of this SSRF vulnerability in Trend Micro Apex Central could be significant, especially for enterprises relying on this product for centralized security management. Successful exploitation could lead to unauthorized disclosure of sensitive information, such as internal network details, security configurations, or credentials stored or accessible via the vulnerable component. This could facilitate lateral movement within the network, targeted attacks, or data breaches. Since the vulnerability does not affect integrity or availability directly, the immediate operational disruption might be limited; however, the confidentiality breach could have severe consequences, including regulatory non-compliance under GDPR, reputational damage, and potential financial penalties. Organizations in sectors with high security requirements, such as finance, healthcare, critical infrastructure, and government, are particularly at risk. The requirement for user interaction lowers the risk somewhat but does not eliminate it, as phishing or social engineering could be used to trigger the exploit. The lack of known exploits in the wild currently reduces immediate risk but should not lead to complacency, as attackers often develop exploits rapidly after public disclosure.

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

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats