# CVE-2026-80513: wpForo Forum < 3.1.6 - Subscriber+ PHP Object Injection via Profile Fields

> Authenticated users can inject PHP objects via profile fields, potentially leading to remote code execution or data manipulation if a suitable gadget chain exists.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-j2rf-55r9-c5ph

## What is CVE-2026-80513?

CVE-2026-80513 is a high-severity unsafe deserialization vulnerability in Unknown wpForo Forum, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The wpForo Forum WordPress plugin before 3.1.6 does not restrict which classes may be instantiated when it deserializes a user-supplied profile field value, allowing authenticated users with Subscriber-level access and above to inject a PHP Object.
No POP chain is present in the wpForo Forum WordPress plugin before 3.1.6 itself; if one is present via another installed wpForo Forum WordPress plugin before 3.1.6 or , this could lead to remote code execution, arbitrary file operations, or SQL injection. This is an incomplete fix of CVE-2026-49769.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-80513 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80513 is a high-severity unsafe deserialization vulnerability in Unknown wpForo Forum, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80513 in the wild and no public exploit code.

Affected product: Unknown wpForo Forum. 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-80513/ (Markdown: https://insights.sbomify.com/CVE-2026-80513/index.md)
```

## Sources

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

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