# CVE-2025-49408: WordPress Templately Plugin <= 3.2.7 - Sensitive Data Exposure Vulnerability

> An attacker can retrieve embedded sensitive data from the Templately WordPress plugin, potentially exposing confidential information to unauthorized users.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-9gc8-9pmh-4936

## What is CVE-2025-49408?

CVE-2025-49408 is a critical vulnerability in WPDeveloper Templately, published on 20 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.2.7.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2025-49408?


## How do I fix CVE-2025-49408?

No fix has been published for CVE-2025-49408 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-49408 being exploited?

There is no known exploitation of CVE-2025-49408 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-49408 and fix it if it is affected.

What it is: CVE-2025-49408 is a critical vulnerability in WPDeveloper Templately, published on 20 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-49408 in the wild and no public exploit code.

Affected product: WPDeveloper Templately. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-49408/ (Markdown: https://insights.sbomify.com/CVE-2025-49408/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-49408
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-49408
- OSV: https://osv.dev/vulnerability/CVE-2025-49408

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-49408/
Summaries are generated and may contain mistakes; the official description above is the record.