Majestic Support <= 1.2.2 - Authenticated (Subscriber+) SQL Injection via 'columns' Parameter
Impact
Majestic Support plugin versions up to 1.2.2 have a SQL injection vulnerability via the 'columns' parameter, allowing authenticated attackers with subscriber-level access to extract sensitive information. The weakness is due to insufficient escaping and preparation of the SQL query. Attackers can exploit this using a whitelisted task and a legitimate nonce.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
ahmadmj · Wordfence
Majestic Support – The Leading-Edge Help Desk & Customer Support Plugin
1 range
ahmadmj · Wordfence
Majestic Support – The Leading-Edge Help Desk & Customer Support Plugin
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0 → through 1.2.2
semver versions
Other versions: unaffected
Original source description
The Majestic Support – The Leading-Edge Help Desk & Customer Support Plugin plugin for WordPress is vulnerable to generic SQL Injection via the 'columns (array keys)' parameter in all versions up to, and including, 1.2.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Any authenticated WordPress user with Subscriber-level access can exploit this because the 'saveusereraserequest' task is whitelisted for front-end customer use, the plugin auto-provisions a help-desk record for every WordPress account, and the only guard is a nonce the attacker legitimately obtains from their own 'Add erase request' page.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-115820View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 2
Assigning organization
Additional data publisher
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.