# CVE-2023-50886: WordPress Legal Pages plugin <= 1.3.7 - CSRF + Broken Access Control vulnerability

> Attackers can trick users into performing unauthorized actions in the Legal Pages plugin due to missing CSRF protection and broken access controls.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-fjmx-p29g-c9jh

## What is CVE-2023-50886?

CVE-2023-50886 is a medium-severity vulnerability in wpWax Legal Pages, published on 15 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cross-Site Request Forgery (CSRF), Incorrect Authorization vulnerability in wpWax Legal Pages.This issue affects Legal Pages: from n/a through 1.3.7.

Weakness: CWE-863 (Incorrect Authorization), CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Wpwax Legal Pages.

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

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

## Is CVE-2023-50886 being exploited?

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

## Other vulnerabilities in wpWax Legal Pages

- [CVE-2023-47824](https://insights.sbomify.com/CVE-2023-47824/): WordPress Legal Pages Plugin <= 1.3.8 is vulnerable to Cross Site Request Forgery (CSRF) (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-50886 is a medium-severity vulnerability in wpWax Legal Pages, published on 15 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-50886 in the wild and no public exploit code.

Affected product: wpWax Legal Pages. 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-50886/ (Markdown: https://insights.sbomify.com/CVE-2023-50886/index.md)
```

## Sources

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

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