dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-13262

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

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 Majestic Support – The Leading-Edge Help Desk & Customer Support Plugin plugin for WordPress is vulnerable to generic SQL Injection via the 'val' parameter in all versions up to, and including, 1.1.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires a valid 'get-smart-reply' nonce, which any Subscriber-level user can obtain by creating a ticket via the public frontend and visiting the resulting ticket detail page, making this effectively exploitable by any authenticated user.

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

SQL injection in the Majestic Support WordPress plugin via the 'val' parameter in versions up to 1.1.9. The vulnerability stems from insufficient input escaping and lack of prepared statements in the SQL query. Attackers need a valid 'get-smart-reply' nonce, which any Subscriber-level user can obtain by creating and viewing a ticket, allowing authenticated users to inject malicious SQL queries and extract sensitive database information.

MitigationUpgrade to a patched version of the Majestic Support plugin that properly escapes the 'val' parameter and uses prepared statements for all database queries. Until a patch is available, restrict Subscriber-level user creation or implement additional server-side access controls.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 Majestic Support plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Majestic Support' in the list. Note the version number displayed.
    Affected if Plugin is installed with version 1.1.9 or lower
  2. Verify the plugin version against the affected range
    Compare the installed version number to the affected range. The vulnerability affects versions up to and including 1.1.9.
    Affected if Installed version is 1.1.9 or any version lower than 1.1.9
  3. Check for existing Subscriber-level user accounts
    In WordPress admin, go to Users > All Users and review the list for any users with the 'Subscriber' role. Alternatively, query the wp_usermeta table filtering for wp_capabilities containing 'subscriber'.
    Affected if There is at least one user with Subscriber-level role who can access the vulnerable endpoint
  4. Confirm the get-smart-reply AJAX endpoint is accessible
    Check if the WordPress AJAX endpoint /wp-admin/admin-ajax.php is reachable and responds to the 'get-smart-reply' action. This is the vulnerable function that processes the 'val' parameter without proper sanitization.
    Affected if The AJAX action 'get-smart-reply' is registered and accessible to authenticated users including Subscribers

A user is affected if they have Majestic Support plugin version 1.1.9 or lower installed AND have at least one Subscriber-level user account that can access the get-smart-reply functionality.

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

Upgrade to a patched version of the Majestic Support plugin that properly escapes the 'val' parameter and uses prepared statements for all database queries. Until a patch is available, restrict Subscriber-level user creation or implement additional server-side access controls.

Recommended fix Moderate confidence

Version 1.2.0 or later

  1. Check the current version of the Majestic Support plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the Majestic Support plugin and verify the current version number
  4. If the installed version is 1.1.9 or earlier, update the plugin to the latest available version
  5. After updating, verify the fix by confirming the plugin version is 1.2.0 or higher
  6. Test that the help desk functionality still works correctly after the update
  7. Ensure any users with Subscriber-level access who do not need help desk privileges have their permissions reviewed
Caveat No known breaking changes for typical usage; always test in staging first

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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