# CVE-2026-15359: Templately < 3.7.1 - Unauthenticated Administrator Templately Cloud Connection Overwrite

> Unauthenticated attackers can overwrite administrator cloud connections in Templately, redirecting template libraries to attacker-controlled content.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-4vxc-ggfm-6c86

## What is CVE-2026-15359?

CVE-2026-15359 is a medium-severity missing authorization vulnerability in Unknown Templately, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Templately  WordPress plugin before 3.7.1 does not have an authorisation check on one of its request handlers, allowing unauthenticated attackers to overwrite the administrator's stored cloud service connection with an account under their control, disconnecting the legitimate administrator and redirecting the site's cloud template library to attacker-controlled content.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-15359?


## How do I fix CVE-2026-15359?

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

## Is CVE-2026-15359 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15359 and fix it if it is affected.

What it is: CVE-2026-15359 is a medium-severity missing authorization vulnerability in Unknown Templately, published on 7 Aug 2026. 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-2026-15359 in the wild and no public exploit code.

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-2026-15359/ (Markdown: https://insights.sbomify.com/CVE-2026-15359/index.md)
```

## Sources

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

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