# CVE-2023-5454: Templately < 2.2.6 - Arbitrary post trashing via Missing Authorization

> Unauthenticated attackers can delete arbitrary posts via an unauthorized REST API call in the Templately WordPress plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Nov 2023
- **Updated:** 26 Feb 2025
- **Also known as:** GHSA-83w6-ppfq-rfhf

## What is CVE-2023-5454?

CVE-2023-5454 is a high-severity missing authorization vulnerability in Unknown Templately, published on 6 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Templately WordPress plugin before 2.2.6 does not properly authorize the `saved-templates/delete` REST API call, allowing unauthenticated users to delete arbitrary posts.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2023-5454?

It affects 1 product.


Products: Templately Templately.

## How do I fix CVE-2023-5454?

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

## Is CVE-2023-5454 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5454 exists.

## Other vulnerabilities in Unknown Templately

- [CVE-2024-47308](https://insights.sbomify.com/CVE-2024-47308/): WordPress Templately plugin <= 3.1.2 - Broken Access Control vulnerability (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5454 and fix it if it is affected.

What it is: CVE-2023-5454 is a high-severity missing authorization vulnerability in Unknown Templately, published on 6 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5454 exists.

Affected product: Unknown 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-2023-5454/ (Markdown: https://insights.sbomify.com/CVE-2023-5454/index.md)
```

## Sources

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

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