# CVE-2026-9722: Laiser Tag <= 1.2.5 - Cross-Site Request Forgery to Plugin Settings Update via Settings Form

> Attackers can trick administrators into updating plugin settings, including API keys, via forged requests due to missing nonce validation.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Jun 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-rh8x-77pm-8pvm

## What is CVE-2026-9722?

CVE-2026-9722 is a medium-severity vulnerability in pcis Laiser Tag, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Laiser Tag plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2.5. This is due to missing or incorrect nonce validation on the addOptionsPageFields function. This makes it possible for unauthenticated attackers to update the plugin's settings, including the API key, tag blacklist, relevance threshold, batch size, and tagging toggles, via a forged request via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-9722 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9722 is a medium-severity vulnerability in pcis Laiser Tag, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-9722 in the wild and no public exploit code.

Affected product: pcis Laiser Tag. 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-9722/ (Markdown: https://insights.sbomify.com/CVE-2026-9722/index.md)
```

## Sources

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

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