CVE-2025-30679
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 · uneditedA 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.
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 · moderate confidenceThis is a Server-side Request Forgery (SSRF) vulnerability in the modOSCE component of Trend Micro Apex Central on-premise. The vulnerability allows attackers to manipulate certain parameters to perform unauthorized requests and potentially disclose sensitive information from the affected system.
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= 2019CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Trend Micro Apex Central installationLocate the Apex Central installation directory or check system inventory for 'Trend Micro Apex Central' softwareAffected if The software is not installed or is a different product
-
Identify installed Apex Central versionCheck the version number of the Apex Central installation - verify if it is exactly version 2019Affected if The installed version is exactly 2019
-
Check modOSCE component presenceExamine the Apex Central installation for the modOSCE component or module - look for modOSCE-related directories, files, or servicesAffected if The modOSCE component is present and installed
-
Verify modOSCE is enabledCheck Apex Central configuration settings or services to determine if modOSCE component is actively enabledAffected if modOSCE is enabled and running
-
Review network configuration for modOSCEInspect network listening ports or proxy settings associated with modOSCE to confirm it can accept external requestsAffected if modOSCE is accessible via network and can make outbound requests
-
Check for indicators of exploitationReview Apex Central logs for suspicious outgoing requests or unauthorized internal network calls originating from the modOSCE componentAffected if Unusual SSRF-style requests appear in logs
A system is affected if it runs Trend Micro Apex Central version 2019 with the modOSCE component enabled, as this combination allows the SSRF vulnerability to be exploited.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor-supplied patches or updates for Trend Micro Apex Central. If no patch is available, implement strict input validation and network segmentation to limit the impact of SSRF exploitation.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30679 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30679 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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