Security Resilience

CVE-2026-42379

Info Disclosure

Published
27 April 2026
Modified
27 April 2026
CVSS Score v3.1 7.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS Score 0.0037 30th percentile
Risk Priority 54 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-42379 is a high-severity Insertion of Sensitive Information Into Sent Data (CWE-201) vulnerability. Its CVSS base score is 7.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Network Sniffing (T1040); ranked at the 30th 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-42379 is an Insertion of Sensitive Information Into Sent Data vulnerability (CWE-201) in the WPDeveloper Templately WordPress plugin, affecting all versions from n/a through 3.6.1. Published on 2026-04-27, it enables the retrieval of embedded sensitive data and carries a CVSS v3.1 base score of 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N), indicating high severity due to network accessibility and significant confidentiality impact.

The vulnerability can be exploited by a low-privileged authenticated user (PR:L) over the network with low attack complexity and no user interaction. Exploitation changes scope (S:C) and results in high confidentiality impact (C:H), allowing the attacker to retrieve sensitive data embedded in sent data without affecting integrity or availability.

Patchstack's advisory at https://patchstack.com/database/wordpress/plugin/templately/vulnerability/wordpress-templately-plugin-3-6-1-sensitive-data-exposure-vulnerability?_s_id=cve documents this sensitive data exposure issue in Templately version 3.6.1, providing details relevant to mitigation and patching for affected WordPress installations.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Insertion of Sensitive Information Into Sent Data vulnerability in WPDeveloper Templately allows Retrieve Embedded Sensitive Data.This issue affects Templately: from n/a through 3.6.1.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1040 Network Sniffing Credential Access
Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-52695Shared CWE-201
CVE-2025-8862Shared CWE-201
CVE-2026-39912Shared CWE-201
CVE-2025-49300Shared CWE-201
CVE-2024-43264Shared CWE-201
CVE-2020-37093Shared CWE-201
CVE-2025-58872Shared CWE-201
CVE-2025-14483Shared CWE-201
CVE-2026-39729Shared CWE-201
CVE-2025-47775Shared 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