# CVE-2026-17014: WP Photo Album Plus < 9.2.07.002 - Unauthenticated Export ZIP File Deletion via delexportzips

> Unauthenticated attackers can delete album export ZIP archives due to missing authorization checks in the WP Photo Album Plus plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 9 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-v9qq-4jqv-3fxp

## What is CVE-2026-17014?

CVE-2026-17014 is a medium-severity missing authorization vulnerability in Unknown WP Photo Album Plus, published on 9 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Photo Album Plus WordPress plugin before 9.2.07.002 does not perform any capability or nonce check on one of its public REST endpoint actions, allowing unauthenticated users to delete the generated album export ZIP archives it stores.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-17014 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17014 is a medium-severity missing authorization vulnerability in Unknown WP Photo Album Plus, published on 9 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-17014 in the wild and no public exploit code.

Affected product: Unknown WP Photo Album Plus. 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-17014/ (Markdown: https://insights.sbomify.com/CVE-2026-17014/index.md)
```

## Sources

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

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