Skip to main content
Menu
CVEs

CVE

Majestic Support stored XSS via ticket message parameter

CVE-2026-126699EUVD-2026-128998GHSA-9R84-V9Q3-V424Published Updated

6.1MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

The Majestic Support – The Leading-Edge Help Desk & Customer Support Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'mjsupport_message' parameter in all versions up to, and including, 1.2.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires that a staff member or administrator opens the affected ticket and clicks the attacker-planted link on the ticket-detail screen, as the VenoBox payload is triggered on click rather than on page load. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.

cve.now Index

18Pcve.now Index 18 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.1/10CVSS 6.1
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 33 if advisories confirm default setups are exposed

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126699 (Majestic Support <= 1.2.4 - Unauthenticated Stored Cross-Site Scripting via 'mjsupport_message' Parameter), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126699 (entry last updated 2026-11-18):
Affected:
- ahmadmj Majestic Support – The Leading-Edge Help Desk & Customer Support Plugin: through 1.2.4
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126699 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126699 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/4bacef02-abec-40c2-a1e1-731aac8014e9?source=cve
- https://plugins.trac.wordpress.org/browser/majestic-support/tags/1.2.4/includes/js/venobox.js#L290
- https://plugins.trac.wordpress.org/browser/majestic-support/tags/1.2.4/modules/ticket/tpls/admin_ticketdetail.php#L1414
- https://plugins.trac.wordpress.org/browser/majestic-support/tags/1.2.4/modules/ticket/model.php#L1285
- https://plugins.trac.wordpress.org/browser/majestic-support/tags/1.2.4/modules/majesticsupport/model.php#L3152
- https://plugins.trac.wordpress.org/browser/majestic-support/tags/1.2.4/modules/ticket/tpls/admin_ticketdetail.php#L3185
- https://wordpress.org/plugins/majestic-support/
- https://plugins.trac.wordpress.org/changeset?reponame=&new=3797624%40majestic-support%2Ftags%2F1.2.5&old=3777716%40majestic-support%2Ftags%2F1.2.4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126699
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126699"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • ahmadmj Majestic Support – The Leading-Edge Help Desk & Customer Support Plugin

    through 1.2.4

Evidence 10

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-126699

Is CVE-2026-126699 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-126699?

Majestic Support – The Leading-Edge Help Desk & Customer Support Plugin: through 1.2.4.Source: cve.now feed data

More CVEs