# CVE-2026-57859: e107 Second-Order Code Execution via eval()-Based Deserialization in e_array::unserialize()

> Attackers with database write access can execute arbitrary PHP code via unsafe deserialization in e107 CMS user preferences.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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:** 30 Jul 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-568x-w5qj-vr7c

## What is CVE-2026-57859?

CVE-2026-57859 is a high-severity code injection vulnerability in e107inc e107, published on 30 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

e107 prior to version 2.3.8 contains a code execution vulnerability in the e_array deserialization handler that allows an attacker with out-of-band database write access to execute arbitrary PHP code by storing a crafted payload in the user_prefs column. The e_array::unserialize() function in e107_handlers/core_functions.php performs only a prefix check for the string 'array' before passing the stored value to eval(), causing automatic PHP execution whenever the affected user's preferences are materialized through e_user_pref::load().

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-57859 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57859 is a high-severity code injection vulnerability in e107inc e107, published on 30 Jul 2026. 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-2026-57859 exists.

Affected product: e107inc e107. 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-57859/ (Markdown: https://insights.sbomify.com/CVE-2026-57859/index.md)
```

## Sources

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

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