dbcve.org
VulnerabilityAwaiting classification

CVE-2026-10835

HIGH · 7.7 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/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 SALESmanago & Leadoo WordPress plugin before 3.11.3 does not properly sanitise and escape a parameter passed to one of its AJAX actions before using it in a SQL statement, and fails to enforce authorisation on that action, allowing authenticated users with minimal permissions, such as subscribers, to perform SQL injection attacks.

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 SALESmanago & Leadoo WordPress plugin before version 3.11.3 contains an authenticated SQL injection vulnerability in one of its AJAX action handlers. The plugin fails to sanitize and escape a user-supplied parameter before incorporating it into a SQL query, and additionally does not enforce proper authorization checks, allowing any authenticated user with subscriber-level permissions to inject malicious SQL code.

MitigationUpdate the SALESmanago & Leadoo WordPress plugin to version 3.11.3 or later. Until the patch is applied, consider restricting user registration or removing subscriber-level accounts if not business-critical.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

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. Identify if SALESmanago & Leadoo plugin is installed
    Navigate to WordPress admin dashboard > Plugins page and look for 'SALESmanago & Leadoo' in the list of installed plugins
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed plugin version
    Click on the plugin name or view the plugin details to read the Version number from the plugin header
    Affected if The version number is lower than 3.11.3 (for example, 3.11.2, 3.11.1, 3.10.x, etc.)
  3. Verify the site allows user registration
    Go to WordPress admin > Settings > General and check if 'Membership' is enabled allowing anyone to register
    Affected if User registration is enabled and the default role is Subscriber or any role that grants authenticated access
  4. Check for existing subscriber-level accounts
    Navigate to WordPress admin > Users page and review the list for accounts with Subscriber role
    Affected if There are one or more user accounts with Subscriber-level permissions or higher
  5. Confirm AJAX handler is accessible
    Attempt to access the WordPress AJAX endpoint (typically /wp-admin/admin-ajax.php) with a low-privilege authenticated request to verify the endpoint responds
    Affected if The AJAX endpoint responds to requests from authenticated users with subscriber-level permissions

You are affected if the SALESmanago & Leadoo plugin version is below 3.11.3 AND your site has at least one authenticated user with subscriber-level access, since the SQL injection can be exploited by any such user.

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 the SALESmanago & Leadoo WordPress plugin to version 3.11.3 or later. Until the patch is applied, consider restricting user registration or removing subscriber-level accounts if not business-critical.

Recommended fix High confidence

SALESmanago & Leadoo WordPress plugin version 3.11.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the SALESmanago & Leadoo plugin
  4. Check the current installed version
  5. If the version is below 3.11.3, click Update Now to upgrade to version 3.11.3
  6. Alternatively, download version 3.11.3 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  7. After updating, verify the new version number in the plugins list
  8. Confirm the plugin is functioning correctly on the site

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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