# CVE-2023-51413: WordPress Piotnet Forms plugin <= 1.0.29 - Broken Access Control vulnerability

> Attackers can access or modify data without proper authorization in the Piotnet Forms WordPress 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:** 12 Jun 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-7mqf-f8fg-5rvr

## What is CVE-2023-51413?

CVE-2023-51413 is a medium-severity missing authorization vulnerability in Piotnet Forms, published on 12 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authorization vulnerability in Piotnet Forms.This issue affects Piotnet Forms: from n/a through 1.0.29.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2023-51413 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-51413 is a medium-severity missing authorization vulnerability in Piotnet Forms, published on 12 Jun 2024. 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-2023-51413 in the wild and no public exploit code.

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

## Sources

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

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