dbcve.org
Enterprise ProtectionApplication · Proofpoint

CVE-2023-5771

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-06
Fix available
A fix is available. Upgrade to 8.18.6 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
Proofpoint Enterprise Protection contains a stored XSS vulnerability in the AdminUI. An unauthenticated attacker can send a specially crafted email with HTML in the subject which triggers XSS when viewing quarantined messages.  This issue affects Proofpoint Enterprise Protection: from 8.20.0 before patch 4796, from 8.18.6 before patch 4795 and all other prior versions.

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 confidence

A stored XSS vulnerability in Proofpoint Enterprise Protection's AdminUI allows unauthenticated attackers to inject malicious HTML/JavaScript through specially crafted email subjects. The payload persists in the quarantine system and executes when administrators view quarantined messages.

MitigationApply vendor patches 4796 (for version 8.20.0+) or 4795 (for version 8.18.6+) to implement proper sanitization of email subject lines before rendering in the AdminUI.

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
Enterprise ProtectionApplication
Affected:< 8.18.6= 8.18.6= 8.20.0

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. Identify Proofpoint Enterprise Protection installation
    Locate the Proofpoint Enterprise Protection installation and note the AdminUI component. This is typically found on the email gateway server.
    Affected if The product Proofpoint Enterprise Protection is installed and running.
  2. Check installed version number
    Access the AdminUI system information page or run the version check command provided by Proofpoint documentation to obtain the exact version number of the Enterprise Protection installation.
    Affected if The installed version is < 8.18.6, exactly 8.18.6, or exactly 8.20.0.
  3. Verify quarantine feature is in use
    Check if the quarantine system is enabled and in use by inspecting the AdminUI quarantine configuration or checking if quarantined messages exist in the system.
    Affected if Quarantine functionality is enabled and there are messages in the quarantine system.
  4. Inspect quarantined message subjects for XSS payloads
    Use the AdminUI quarantine viewer or query the quarantine database/logs to examine the subject lines of quarantined emails. Look for HTML tags, script elements, or encoded JavaScript in subject fields.
    Affected if Quarantined messages contain unsanitized HTML or JavaScript in their subject line fields.
  5. Confirm AdminUI access for administrators
    Verify that administrator accounts can access the AdminUI quarantine view where quarantined message subjects are displayed.
    Affected if Administrators have access to view quarantined messages through the AdminUI.

A user is affected if running a vulnerable version (< 8.18.6, 8.18.6, or 8.20.0) of Proofpoint Enterprise Protection with the quarantine feature enabled and admins accessing the AdminUI to view quarantined message subjects.

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 8.18.6 or later
Fixed in 8.18.6
Interim mitigation

Apply vendor patches 4796 (for version 8.20.0+) or 4795 (for version 8.18.6+) to implement proper sanitization of email subject lines before rendering in the AdminUI.

Recommended fix High confidence

8.18.6 with patch 4795 or 8.20.0 with patch 4796

  1. Contact Proofpoint support to obtain patch 4795 for version 8.18.6
  2. Apply patch 4795 to Proofpoint Enterprise Protection 8.18.6 installations
  3. Contact Proofpoint support to obtain patch 4796 for version 8.20.0
  4. Apply patch 4796 to Proofpoint Enterprise Protection 8.20.0 installations
  5. For all prior versions (before 8.18.6), upgrade to a supported version (8.18.6 or 8.20.0) then apply the corresponding patch

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

Fix this in Enterprise Protection Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-5771 — 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-5771 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