# CVE-2024-56291: WordPress PlainInventory – Inventory Management Plugin Plugin <= 3.1.6 - PHP Object Injection vulnerability

> An attacker can exploit PHP object injection in the PlainInventory plugin to potentially execute arbitrary code on the WordPress site.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jan 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-9x5c-5jg6-mcv6

## What is CVE-2024-56291?

CVE-2024-56291 is a high-severity unsafe deserialization vulnerability in plainware PlainInventory, published on 7 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Deserialization of Untrusted Data vulnerability in plainware PlainInventory z-inventory-manager allows Object Injection.This issue affects PlainInventory: from n/a through <= 3.1.6.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-56291?


## How do I fix CVE-2024-56291?

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

## Is CVE-2024-56291 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-56291 and fix it if it is affected.

What it is: CVE-2024-56291 is a high-severity unsafe deserialization vulnerability in plainware PlainInventory, published on 7 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-56291 exists.

Affected product: plainware PlainInventory. 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-2024-56291/ (Markdown: https://insights.sbomify.com/CVE-2024-56291/index.md)
```

## Sources

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

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