dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-6235

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
The Sendmachine for WordPress plugin for WordPress is vulnerable to authorization bypass via the 'manage_admin_requests' function in all versions up to, and including, 1.0.20. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to overwrite the plugin's SMTP configuration, which can be leveraged to intercept all outbound emails from the site (including password reset emails).

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

The Sendmachine WordPress plugin has an authorization bypass vulnerability in its 'manage_admin_requests' function in versions up to 1.0.20. The plugin fails to properly verify user authorization before allowing modifications to SMTP configuration settings, enabling unauthenticated attackers to change email server settings and intercept all outbound emails including password reset messages.

MitigationUpdate to the latest version of the Sendmachine plugin once available, or disable the plugin until a patch is released. If the site may have been compromised, audit SMTP configuration, change credentials, and review access logs for unauthorized access.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Verify Sendmachine plugin is installed
    Check if the Sendmachine plugin directory exists in wp-content/plugins/ on the WordPress server
    Affected if The Sendmachine plugin directory is present on the server
  2. Determine installed plugin version
    Open the main Sendmachine plugin file (usually sendmachine.php) and locate the version comment or Version: header in the file metadata
    Affected if The reported version is 1.0.20 or lower
  3. Confirm the vulnerable function exists
    Search the plugin source code for the function 'manage_admin_requests' to verify it exists in the installed version
    Affected if The function 'manage_admin_requests' is present in the plugin code
  4. Inspect SMTP configuration for unauthorized changes
    Query the WordPress database wp_options table for rows where option_name contains 'smtp', 'sendmachine', or 'mail' settings; review current values for any unexpected domains or credentials
    Affected if SMTP settings have been modified to unfamiliar values or contain attacker-controlled parameters

A user is affected if the Sendmachine plugin version is 1.0.20 or lower and the 'manage_admin_requests' function is present and exposed, particularly if SMTP settings show unexpected modifications.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of the Sendmachine plugin once available, or disable the plugin until a patch is released. If the site may have been compromised, audit SMTP configuration, change credentials, and review access logs for unauthorized access.

Recommended fix High confidence

Version 1.0.21 or latest available release

  1. Update the Sendmachine for WordPress plugin to the latest available version (1.0.21 or higher) from the WordPress plugin repository
  2. After updating, navigate to the plugin settings and verify that the SMTP configuration is correct
  3. As a security precaution, consider resetting SMTP credentials (username, password, API keys) that may have been exposed or modified
  4. Review server access logs for any unauthorized SMTP configuration changes that may indicate exploitation attempts
  5. Monitor outbound email traffic for any suspicious activity

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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