Skip to main content
VulnerabilityPublished

CVE-2026-42379: Templately (WordPress plugin) · Insertion of Sensitive Information Into Sent Data

Affects Templately (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.7 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
WPDeveloperTemplatelyAffected
  • ≥ n/a, < 3.6.2
Fixed in–

AI-suggested

Until an official fix is released, users should consider limiting access privileges to trusted users only and monitor for any suspicious activity related to data exposure. Avoid exposing the plugin to untrusted networks if possible.

Description

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.

References

Community reviews

Loading reviews…