# CVE-2026-14821: Quiz And Survey Master < 11.1.5 - Contributor+ Arbitrary Template Deletion

> Contributor-level users can delete arbitrary output templates due to missing capability checks in the Quiz and Survey Master WordPress plugin.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-v9qq-hpjj-75m3

## What is CVE-2026-14821?

CVE-2026-14821 is a low-severity missing authorization vulnerability in Unknown Quiz and Survey Master (QSM), published on 28 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Quiz and Survey Master (QSM)  WordPress plugin before 11.1.5 does not perform a capability check before deleting output templates, allowing users with contributor-level access and above to delete arbitrary templates.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-14821 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14821 is a low-severity missing authorization vulnerability in Unknown Quiz and Survey Master (QSM), published on 28 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14821 exists.

Affected product: Unknown Quiz and Survey Master (QSM). 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-14821/ (Markdown: https://insights.sbomify.com/CVE-2026-14821/index.md)
```

## Sources

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

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