# CVE-2022-3451: Product Stock Manager < 1.0.5 - Subscriber+ Unauthorised AJAX Calls

> Subscribers can perform unauthorized actions and modify arbitrary options due to missing authorization and CSRF checks in AJAX handlers.

- **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:** 7 Nov 2022
- **Updated:** 1 May 2025
- **Also known as:** GHSA-f6x7-qg62-r396

## What is CVE-2022-3451?

CVE-2022-3451 is a medium-severity missing authorization vulnerability in Unknown Product Stock Manager, published on 7 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Product Stock Manager WordPress plugin before 1.0.5 does not have authorisation and proper CSRF checks in multiple AJAX actions, allowing users with a role as low as subscriber to call them. One action in particular could allow to update arbitrary options

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2022-3451?

It affects 1 product.


Products: Addify Product Stock Manager.

## How do I fix CVE-2022-3451?

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

## Is CVE-2022-3451 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3451 and fix it if it is affected.

What it is: CVE-2022-3451 is a medium-severity missing authorization vulnerability in Unknown Product Stock Manager, published on 7 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3451 exists.

Affected product: Unknown Product Stock Manager. 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-2022-3451/ (Markdown: https://insights.sbomify.com/CVE-2022-3451/index.md)
```

## Sources

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

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