dbcve.org
Apex CentralApplication · Trendmicro

CVE-2025-30680

HIGH · 7.1 CVSS v3.1 Published 2025-06-17
Fix available
A fix is available. Upgrade to 2025-03-01 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a Server-side Request Forgery (SSRF) vulnerability in Trend Micro Apex Central affecting only the SaaS deployment. Attackers can manipulate certain request parameters to cause the server to make unintended requests to internal or external resources, leading to information disclosure.

MitigationCustomers using Apex Central SaaS should ensure automatic monthly maintenance releases are enabled, which Trend Micro applies automatically. No additional action is required if auto-updates are configured.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Apex CentralApplication
Affected:< 2025-03-01

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Apex Central deployment type
    Log into the Apex Central console and navigate to Administration > Settings > Product Information. Look for the deployment type indicator (SaaS or On-Premise).
    Affected if The deployment type shows "SaaS" - only SaaS deployments are affected by this vulnerability.
  2. Check your SaaS maintenance release date
    In the Apex Central SaaS console, go to Administration > Settings > Product Information. Locate the "Last Maintenance Release" or "Version" field. Alternatively, contact your Trend Micro representative or support to confirm the maintenance release date.
    Affected if The maintenance release date is before March 1, 2025, or the version/build is older than the March 2025 release.
  3. Review outbound request logs for suspicious patterns
    Examine Apex Central audit logs or network traffic logs for outbound requests from the server to internal IP ranges (such as 10.x.x.x, 192.168.x.x, 127.x.x.x) or unusual external destinations. Look for requests initiated by users that do not correlate with legitimate operations.
    Affected if You find outbound server requests to internal infrastructure or unexpected external URLs that were not initiated by legitimate administrative actions.

You are affected if you are using Apex Central SaaS and your maintenance release date is before March 1, 2025, or if you observe unexplained outbound server requests in your logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2025-03-01 or later
Fixed in 2025-03-01
Interim mitigation

Customers using Apex Central SaaS should ensure automatic monthly maintenance releases are enabled, which Trend Micro applies automatically. No additional action is required if auto-updates are configured.

Recommended fix High confidence

Apex Central (SaaS) 2025-03-01 or later

  1. 1. Confirm you are using Apex Central SaaS (this vulnerability does NOT affect on-premises installations)
  2. 2. Verify your SaaS instance is on the 2025-03-01 monthly maintenance release or later
  3. 3. If automatic monthly maintenance updates are enabled (default setting), no action required - the fix is already applied
  4. 4. If manual updates are used, contact Trend Micro support to ensure the March 2025 or later update is applied
  5. 5. Confirm the version through the Apex Central console or support

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Apex Central Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30680 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30680 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data