CVE-2026-13262 json
Majestic Support <= 1.1.9 - Authenticated (Subscriber+) SQL Injection via 'val' Parameter
published 2026-07-11 3 mo ago modified 2026-07-13 3 mo ago also EUVD-2026-43122
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 mo ago
Exploit prediction
0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- ahmadmj Majestic Support – The Leading-Edge Help Desk & Customer Support Plugin
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/502577dd-49e3-419d-8b37-591be69ad131?source=cve
- plugins.trac.wordpress.org /browser/majestic-support/tags/1.1.8/includes/ajax.php#L19
- plugins.trac.wordpress.org /browser/majestic-support/tags/1.1.9/modules/smartreply/model.php#L184
- plugins.trac.wordpress.org /browser/majestic-support/tags/1.1.9/modules/smartreply/model.php#L183
- plugins.trac.wordpress.org /browser/majestic-support/tags/1.1.9/includes/ajax.php#L19
- plugins.trac.wordpress.org /browser/majestic-support/tags/1.1.9/modules/ticket/tpls/ticketdetail.php#L672
- plugins.trac.wordpress.org /browser/majestic-support/tags/1.1.8/modules/smartreply/model.php#L184
- plugins.trac.wordpress.org /browser/majestic-support/tags/1.1.8/modules/smartreply/model.php#L183
- plugins.trac.wordpress.org /browser/majestic-support/tags/1.1.8/modules/ticket/tpls/ticketdetail.php#L672
- plugins.trac.wordpress.org /browser/majestic-support/tags/1.2.0/modules/smartreply/model.php?rev=3599140#L212
Sources
- CVE List CVE-2026-13262
- NVD CVE-2026-13262
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.