dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-4162

HIGH · 7.1 CVSS v3.1 Published 2026-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable 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 Gravity SMTP plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 2.1.4. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to uninstall and deactivate the plugin and delete plugin options. NOTE: This vulnerability is also exploitable via a Cross-Site Request Forgery vector.

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 confidence

The Gravity SMTP WordPress plugin lacks proper capability checks on endpoints that handle plugin uninstallation, deactivation, and deletion of plugin options. This allows any authenticated user with subscriber-level permissions (the lowest WordPress role) to perform these administrative actions, making the plugin unusable or causing data loss. The vulnerability is also exploitable via Cross-Site Request Forgery, enabling unauthenticated attackers to trick logged-in users into performing these actions.

MitigationApply the vendor patch when available. In the interim, disable new user registration or remove subscriber-level accounts, and consider deploying a WAF with virtual patching for this vulnerability.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

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

  1. Verify Gravity SMTP plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Gravity SMTP'. Note the installed version number.
    Affected if The plugin is installed and the version is unpatched (compare to any vendor advisory).
  2. Identify subscriber-level user accounts
    Go to Users > All Users in WordPress admin. Look for any users with the 'Subscriber' role.
    Affected if At least one subscriber-level account exists in the system, enabling authenticated exploitation.
  3. Confirm endpoint accessibility via capability check review
    Inspect plugin code or use a role tester to verify whether subscriber-role requests to wp-admin/admin-post.php or ajax endpoints trigger uninstall/deactivation/delete actions without proper authorization.
    Affected if Subscriber users can trigger uninstall, deeletion, or option deletion actions without administrator privileges.
  4. Test for CSRF vulnerability in plugin actions
    Log in as a subscriber, then attempt an action via a crafted external request (or inspect the plugin forms for missing CSRF tokens/nonces).
    Affected if Plugin actions lack anti-CSRF tokens, allowing unauthenticated exploitation via tricking logged-in users.

A user is affected if Gravity SMTP is installed with an unpatched version and at least one subscriber account exists or the site has visitors who could be targeted via CSRF.

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

Apply the vendor patch when available. In the interim, disable new user registration or remove subscriber-level accounts, and consider deploying a WAF with virtual patching for this vulnerability.

Recommended fix Moderate confidence

Gravity SMTP version 2.1.5 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the Gravity SMTP plugin
  4. 4. Check the current version number to confirm it is 2.1.4 or below
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Verify the update was successful and the plugin functions correctly
  7. 7. Test that the plugin's core functionality (sending emails via SMTP) still works after the update

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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