Threats / Trend Micro / CVE-2023-41179
CVE-2023-41179
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Trend Micro Apex One and Worry-Free Business Security vulnerability
Trend Micro Apex One and Worry-Free Business Security contain a vulnerability in a third-party anti-virus uninstaller allowing remote code execution when an attacker has administrative console access.
Verdict
Today item — known-exploited.
An authenticated attacker with administrative console access can manipulate the uninstaller module to execute arbitrary code on protected systems. This requires prior compromise of administrative credentials or console access.
CISA KEV Yes · 2023-09-214EPSS 0.04739 (verify live)5CVSS 7.2 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-09-21).
Probability (EPSS)
EPSS 0.04739 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.2 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) · Affected: Trend Micro, Apex One and Worry-Free Business Security. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 2 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I obtain or compromise administrative console credentials for the target environment.
Business
Administrative access controls are bypassed, expanding the attack surface within the security infrastructure.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I manipulate the third-party anti-virus uninstaller module through the administrative console.
Business
The security product's own management interface becomes a vector for code execution.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute arbitrary code on protected systems via the compromised uninstaller.
Business
Protected endpoints are compromised despite the security product being installed, undermining the organization's defense posture.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by trendmicroCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.