basicsecurity.net
Proof, not just disclosure.
Threats / Trend Micro / CVE-2023-41179
CVE-2023-41179 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-213EPSS 0.04739 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported 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).
CISA KEV ↗Confirmed
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
Affected: Trend Micro, Apex One and Worry-Free Business Security. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 3 reported-exploitation source(s)
  • Catalogued by trendmicro (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by trendmicroCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.