---
id: "CVE-2026-115820"
kind: "vulnerability"
aliases: ["CVE-2026-115820"]
title: "Majestic Support WordPress plugin: SQL injection lets subscribers read database"
severity: "medium"
cvss: 6.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["majestic-support", "package", "self-hosted", "wordpress"]
not_affected_if: ["plugin-not-installed", "registration-closed", "version-above-1.2.2"]
published_at: "2026-10-30T18:17:23+00:00"
first_seen_at: "2026-10-30T18:55:29+00:00"
updated_at: "2026-10-30T18:57:01+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-115820", "first_seen_at": "2026-10-30T18:55:29+00:00"}]
---

# Majestic Support WordPress plugin: SQL injection lets subscribers read database

The Majestic Support help desk plugin for WordPress up to and including 1.2.2 passes a user-supplied 'columns' array key into a SQL query without proper escaping or preparation. An authenticated attacker with Subscriber-level access can append extra SQL queries to extract sensitive data from the site's database.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Majestic Support plugin version in the WordPress admin under Plugins; versions up to and including `1.2.2` are affected.
- Confirm whether open user registration allows Subscriber accounts on the site.

## Fix

- Majestic Support plugin: unknown; the sources do not state a fixed version.

## Timeline

- 2026-10-30T18:55:29+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-115820

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_