Security Resilience

CVE-2026-27406

Info Disclosure

Published
05 March 2026
Modified
22 April 2026
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0044 37th percentile
Risk Priority 57 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-27406 is a high-severity Insertion of Sensitive Information Into Sent Data (CWE-201) vulnerability. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Cloud Instance Metadata API (T1552.005); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-27406 is an Insertion of Sensitive Information Into Sent Data vulnerability (CWE-201) in the My Tickets WordPress plugin by Joe Dolson. The issue affects versions from n/a through 2.1.0 and allows attackers to retrieve embedded sensitive data.

With a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), the vulnerability can be exploited over the network by unauthenticated attackers requiring low complexity and no user interaction. Exploitation enables retrieval of sensitive information with high confidentiality impact but no disruption to integrity or availability.

The Patchstack advisory at https://patchstack.com/database/Wordpress/Plugin/my-tickets/vulnerability/wordpress-my-tickets-plugin-2-1-0-sensitive-data-exposure-vulnerability?_s_id=cve documents this sensitive data exposure issue in My Tickets version 2.1.0.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Insertion of Sensitive Information Into Sent Data vulnerability in Joe Dolson My Tickets my-tickets allows Retrieve Embedded Sensitive Data.This issue affects My Tickets: from n/a through <= 2.1.0.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1552.005 Cloud Instance Metadata API Credential Access
Adversaries may attempt to access the Cloud Instance Metadata API to collect credentials and other sensitive data.
T1040 Network Sniffing Credential Access
Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network.
T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1591.001 Determine Physical Locations Reconnaissance
Adversaries may gather the victim's physical location(s) that can be used during targeting.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-24582Shared CWE-201
CVE-2025-59509Shared CWE-201
CVE-2026-65543Shared CWE-201
CVE-2026-104385Shared CWE-201
CVE-2024-53804Shared CWE-201
CVE-2023-3413Shared CWE-201
CVE-2025-55710Shared CWE-201
CVE-2024-31200Shared CWE-201
CVE-2025-53988Shared CWE-201
CVE-2026-1694Shared CWE-201

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)
  • V14.2.3

Mitigating Controls (NIST 800-53 r5) AI

Directly enforces policy-based information flow rules that block transmission of sensitive data to unauthorized actors.

Enforces authorizations on logical access so that sensitive data is not released to unauthorized recipients.

Requires validation of outbound information to ensure sensitive content is not disclosed in responses or messages.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly prevent insertion of sensitive data into application outputs and messages.

DE.CM-09 partial match
blocks

Monitoring runtime data flows and outputs can detect sensitive data being transmitted.

PR.DS-02 partial match
blocks

Protecting data-in-transit can include filtering or encrypting to avoid exposing sensitive content.

PR.DS-10 partial match
blocks

Protecting data-in-use includes removing confidential values before they are processed or sent.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

Data-masking techniques can prevent sensitive values from appearing in transmitted payloads.

prevents

Secure-coding standards explicitly forbid hard-coded or unfiltered sensitive data in outbound messages.

References