CVE-2025-54948
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.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. OS command injection puts shell syntax into the request. WAF rules catch common shell commands but miss encoded or unusual payloads.
Also consider: shlex/execve-style APIs
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-54948 being exploited?
Yes. CVE-2025-54948 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-54948?
CVE-2025-54948 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-54948?
Yes. A fix has been recorded for CVE-2025-54948. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-54948 affect?
CVE-2025-54948 affects trendmicro:apex_one. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 2019 (14.0) and < 14.0.0.14039
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 18 Aug 2025 (SSVC 2.0.3).
timeline
- 5 Aug 2025Published
- 18 Aug 2025Added to CISA KEV (exploited in the wild) · 12 days later
- 18 Aug 2025CISA SSVC assessment: exploitation active · 1 day later
- 8 Sept 2025CISA remediation due date (US federal agencies) · 20 days later
- 21 Oct 2025CVE record last updated · 44 days later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Linksuccess.trendmicro.com /en-US/solution/KA-0020652
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-54948
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.