CVE-2023-0089
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 · uneditedThe webutils in Proofpoint Enterprise Protection (PPS/POD) contain a vulnerability that allows an authenticated user to execute remote code through 'eval injection'. This affects all versions 8.20.0 and below.
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 · high confidenceThe webutils component in Proofpoint Enterprise Protection (PPS/POD) versions 8.20.0 and below contains an eval injection vulnerability allowing authenticated users to execute arbitrary code. User-supplied input is passed to an eval() function without proper sanitization, enabling remote code 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< 8.13.22>= 8.18.0, < 8.18.4= 8.18.6= 8.20.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Proofpoint Enterprise Protection versionUse the product's administrative interface, CLI tool, or system information file to determine the exact version number of Proofpoint Enterprise Protection (PPS/POD)Affected if The installed version falls into any of these ranges: < 8.13.22, >= 8.18.0 and < 8.18.4, = 8.18.6, or = 8.20.0
-
Confirm the webutils component is enabledCheck the Proofpoint configuration files or administrative console for the webutils module/component statusAffected if webutils is present and enabled in the configuration
-
Verify user authentication is configured for the web interfaceInspect the authentication settings in the Proofpoint administrative panel or configuration to determine if user accounts with access to webutils existAffected if User authentication is enabled and valid users can access the system (the vulnerability requires an authenticated session)
-
Review access logs for webutils endpointsSearch authentication and access logs for requests to webutils-related paths, particularly those containing unusual parameters or code-like patterns
You are affected if your installed version matches any of the vulnerable ranges (< 8.13.22, >= 8.18.0 to < 8.18.4, 8.18.6, or 8.20.0), webutils is enabled, and user authentication is configured.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data8.13.228.18.4
Upgrade Proofpoint Enterprise Protection to a version above 8.20.0. Until patched, restrict administrative access to trusted personnel only and monitor for suspicious command execution.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0089 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-0089 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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