CVE-2023-33999
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 · uneditedImproper neutralization of input during web page generation ('cross-site scripting') vulnerability in WPVibes WP Mail Log allows DOM-Based XSS. This issue affects WP Mail Log: from n/a through 1.0.2.
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 confidenceDOM-based XSS vulnerability in WPVibes WP Mail Log WordPress plugin allows injection of arbitrary JavaScript via unsanitized user input that gets rendered directly in the browser's DOM without server-side validation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Confirm WP Mail Log plugin is installedNavigate to WordPress admin Dashboard > Plugins > Installed Plugins. Look for 'WPVibes WP Mail Log' or 'WP Mail Log' in the list of installed plugins.Affected if Plugin appears in the installed plugins list
-
Check the installed version numberIn the plugins list, click on the plugin to view details, or look at the plugin file header in wp-content/plugins/wp-mail-log/.../wp-mail-log.php to find the Version: x.x.x entry.Affected if Version is older than the patched version (the vendor released a fix that addresses the DOM-based XSS)
-
Verify plugin is activeIn WordPress admin > Plugins, confirm the plugin status shows 'Active' rather than 'Inactive' or 'Must-Use'.Affected if Plugin is active - only active plugins process user input and render output vulnerable to XSS
-
Inspect mail log entries for unsanitized input renderingAccess the mail log page created by the plugin (usually under a 'Mail Log' or similar admin menu). View page source in browser (right-click > View Page Source) and search for log content being rendered inside HTML without proper encoding.Affected if Log entries containing special characters like < > " ' display raw in the DOM without HTML entity encoding
-
Check plugin code for direct DOM manipulation of user inputIf you have file access, examine the main plugin PHP file for functions that output mail sender, subject, or body content directly into HTML without using functions like esc_html(), esc_attr(), or wp_kses(). Look for echo or print statements outputting $_POST, $_GET, or mail headers.Affected if Code contains raw output of mail parameters (From, To, Subject, Body) without sanitization functions
A user is affected if the WPVibes WP Mail Log plugin is installed, active, and running a version prior to the vendor fix that lacks proper input sanitization on mail data rendered in the browser.
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 dataUpdate WP Mail Log to the latest patched version; if no patch exists, locate and sanitize the vulnerable JavaScript code handling user input using proper output encoding methods.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33999 — 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-33999 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