dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-3829

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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 WP Encryption – One Click Free SSL Certificate & SSL / HTTPS Redirect, Security & SSL Scan plugin for WordPress is vulnerable to unauthorized modification of data due to missing capability checks on the 'wple_basic_get_requests' function in all versions up to, and including, 7.8.5.10. This makes it possible for authenticated attackers, with subscriber level access and above, to reset the SSL setup state, force SSL to appear complete, and modify plan selection options.

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 WP Encryption WordPress plugin lacks proper capability checks on the 'wple_basic_get_requests' function, allowing any authenticated user with subscriber-level access or higher to call this function. This enables attackers to reset SSL setup state, force SSL to appear complete, and modify plan selection options through unauthorized data modification.

MitigationUpdate to version 7.8.5.11 or later which includes proper capability checks. Until then, consider restricting user registration or removing subscriber-level accounts unless necessary.

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
Low
Availability
Low

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

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

  1. Confirm WP Encryption plugin is installed
    Check WordPress admin under Plugins > Installed Plugins, or verify the /wp-content/plugins/wp-encryption/ directory exists on the server
    Affected if Plugin is present in the WordPress installation
  2. Identify installed plugin version
    View plugin details in WordPress admin plugins page, or open the main plugin PHP file and locate the 'Version' field in the plugin header comment
    Affected if Version is lower than 7.8.5.11
  3. Verify user accounts with subscriber or higher roles exist
    Access WordPress admin under Users > All Users and review the list of existing accounts and their assigned roles
    Affected if At least one user with Subscriber, Contributor, Author, Editor, or Administrator role exists in WordPress
  4. Confirm the vulnerable function is accessible
    The vulnerability lies in the wple_basic_get_requests function lacking capability checks - this can be verified by reviewing plugin code if direct file access is available, or by confirming the plugin is active and accepts REST API or admin-ajax requests
    Affected if Plugin is active and the wple_basic_get_requests function is present without proper authorization checks

The environment is affected if the WP Encryption plugin is installed and active with a version earlier than 7.8.5.11 and at least one user account with subscriber-level access or higher exists in WordPress

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 version 7.8.5.11 or later which includes proper capability checks. Until then, consider restricting user registration or removing subscriber-level accounts unless necessary.

Recommended fix High confidence

Version newer than 7.8.5.10 (check WordPress plugin repository for latest stable release)

  1. Check your current WP Encryption plugin version in WordPress admin under Plugins
  2. If the installed version is 7.8.5.10 or lower, navigate to Plugins > Add New > Upload Plugin or use the WordPress plugin repository to update to the latest version
  3. Verify the update was successful by confirming the new version number
  4. Test that the SSL functionality still works correctly after the update
  5. Ensure that the 'wple_basic_get_requests' function now includes proper capability checks (normally verified by the plugin developer, but you can confirm by testing that lower-privileged users cannot modify SSL settings)
Caveat Minor - verify SSL certificate renewal/management functions work normally after upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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