Wp Mail LogWordPress extension · Wpvibes
CVE-2022-45807
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 · uneditedCross-Site Request Forgery (CSRF) in WPVibes WP Mail Log plugin <= 1.0.1 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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in WPVibes WP Mail Log WordPress plugin versions 1.0.1 and below allows remote attackers to induce authenticated administrators to perform unintended actions via crafted requests.
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
Wp Mail LogWordPress extension
< 1.0.2CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Locate the WP Mail Log plugin installationCheck the WordPress plugins directory at wp-content/plugins/ for a folder named 'wp-mail-log' or similar, or query the WordPress database wp_options table for option_name containing 'active_plugins'Affected if The plugin folder exists in the plugins directory or is listed in WordPress active plugins
-
Identify the installed plugin versionOpen the main plugin PHP file (usually wp-content/plugins/wp-mail-log/wp-mail-log.php or similar) and read the 'Version' field from the plugin header comments at the top of the fileAffected if The version number displayed is 1.0.1 or lower (e.g., 1.0.1, 1.0.0)
-
Verify WordPress admin access is possibleConfirm that the WordPress site has an active admin dashboard accessible at /wp-admin/ and that administrator accounts exist on the siteAffected if The site has an active WordPress admin panel with administrator user accounts, which is required for the CSRF attack to target authenticated sessions
-
Confirm the plugin handles admin actionsReview whether the plugin exposes any admin action URLs (typically in settings pages or via AJAX endpoints) that perform state-changing operations without requiring nonce verificationAffected if The plugin contains admin functionality that processes requests without validating anti-CSRF tokens (nonces)
You are affected if the WP Mail Log plugin is installed with version 1.0.1 or below and your site has an accessible WordPress admin area with active administrator accounts.
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.
dbcve · scoped1.0.2
Update the plugin to the latest version beyond 1.0.1; verify that all state-changing requests include anti-CSRF token validation.
WP Mail Log version 1.0.2
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the "WP Mail Log" plugin by WPVibes
- Check the current version number to confirm it is <= 1.0.1
- If an update is available, click "Update Now" to upgrade to version 1.0.2
- Alternatively, go to Plugins > Add New > Upload Plugin and upload version 1.0.2 of the WP Mail Log plugin
- Verify the plugin now shows version 1.0.2 after updating
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Mail Log
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45807 — 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-2022-45807 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