dbcve.org
Apex OneApplication · Trendmicro

CVE-2023-52330

MEDIUM · 6.1 CVSS v3.1 Published 2024-01-23
Fix available
A fix is available. Upgrade to 14.0.12849 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A cross-site scripting vulnerability in Trend Micro Apex Central could allow a remote attacker to execute arbitrary code on affected installations of Trend Micro Apex Central. Please note: user interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

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 confidence

A stored cross-site scripting (XSS) vulnerability exists in Trend Micro Apex Central's web interface. An attacker can inject malicious JavaScript code through a vulnerable input field, which gets stored in the application and executes when authenticated users view the compromised content, allowing arbitrary code execution in the context of the victim's browser session.

MitigationApply the vendor-provided security patch for CVE-2023-52330. Until patched, implement input validation and output encoding on user-supplied data, and configure Content Security Policy headers to mitigate XSS execution.

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
Apex OneApplication
Affected:< 14.0.12849= 2019

CVSS 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Trend Micro Apex One installation
    Check Windows Services for 'Trend Micro Apex One' service or look for Apex One in Add/Remove Programs. The product may also be listed as 'Apex One' or 'OfficeScan' (older naming).
    Affected if Apex One or Apex Central is installed and the web console is accessible
  2. Identify installed Apex One version
    Access the Apex One web console, then navigate to Updates > Component Status or Help > About to view the exact build number. Alternatively, check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\Apex One\CurrentVersion or check the version info in the installation directory.
    Affected if The displayed version is below 14.0.12849 or shows as version 2019 (year-based release)
  3. Verify web console is enabled
    Ensure the Apex One web console port (typically 4343 or 443) is accessible and the service is running. Check via Services.msc that the 'Apex One HTTP Service' or similar is started.
    Affected if The web interface is enabled and accessible to users
  4. Identify user-accessible input fields
    Log into the Apex One web console as a standard user (not admin) and navigate to policy settings, custom notifications, or dashboard widgets where users can input custom text. These are typical stored XSS entry points.
    Affected if Standard authenticated users can input custom content that gets stored and displayed to other users

You are affected if Apex One or Apex Central is installed with a version below 14.0.12849 or equal to 2019, and the web interface is accessible to authenticated users who can input custom content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 14.0.12849 or later
Fixed in 14.0.12849
Interim mitigation

Apply the vendor-provided security patch for CVE-2023-52330. Until patched, implement input validation and output encoding on user-supplied data, and configure Content Security Policy headers to mitigate XSS execution.

Recommended fix High confidence

Apex One version 14.0.12849 or later (including any subsequent security patches)

  1. 1. Log in to the Trend Micro Apex One server with administrator credentials
  2. 2. Navigate to the administration console or patch management section
  3. 3. Check the current installed version under System Settings > About or similar
  4. 4. Download the latest Apex One patch or service pack from the Trend Micro Download Center at success.trendmicro.com
  5. 5. Apply the update following Trend Micro's standard patch deployment procedures
  6. 6. Verify the installation completed successfully by checking the version number again
  7. 7. Test that the Apex Central management console is accessible and functioning normally
Caveat Standard upgrade precautions apply - back up your configuration and test in a non-production environment before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Apex One Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-52330 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-52330 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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