CVE-2025-54987
Exploitation reported by one source. First attested on 2025-08-06 by GCVE · kevintel.
- Published2025-08-05
- WeaknessCWE-78
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
A vulnerability in Trend Micro Apex One (on-premise) management console could allow a pre-authenticated remote attacker to upload malicious code and execute commands on affected installations. This vulnerability is essentially the same as CVE-2025-54948 but targets a different CPU architecture.
Timeline
dates in UTC- 2025-08-0513:15CVE publishedNVD
- 2025-08-0615:30Listed as exploited by GCVEGCVE
- 2025-08-0615:30Exploitation first reportedGCVE
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2019.x | = 2019 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As trendmicro, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- Trend Micro, Inc. Trend Micro Apex OneAffected
- ≥ 2019 (14.0), < 14.0.0.14039fixed in 14.0.0.14039semver
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-08-05
Fix
Advisories and patches
- success.trendmicro.comPatch · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-10
- Metasploit modules
- none listed Metasploit Framework
Sources
- GCVEexploitation2025-08-06
- CISA-ADPSSVC decisionnone2025-08-06
- CNACVSS 3.19.4known since 2026-10-23
- NVDCVSS 3.19.8read 2026-10-23
- CNAweakness (CWE)CWE-78known since 2026-10-23
- FIRST EPSSEPSS score27.3 %read 2026-11-10
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2025-23620same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-8q59-7jj3-fj58same flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2025-08-05
- Last Modified
- 2026-06-17
- NVD status
- Analyzed
- GitHub Advisory
- GHSA-8q59-7jj3-fj58
Frequently asked questions
What is CVE-2025-54987?
Is CVE-2025-54987 actively exploited?
What is the CVSS score for CVE-2025-54987?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GCVE · GCVE dump terms (preserve source attribution)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-8q59-7jj3-fj58
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- CISA Vulnrichment · CC0-1.0