# CVE-2026-114624: baserCMS: PHP object injection via unguarded unserialize() in the widget-area entity


- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-xf6p-r2hc-cc6w

## What is CVE-2026-114624?

CVE-2026-114624 is a high-severity vulnerability in baserproject basercms, published on 23 Oct 2026. 

### Official description

baserCMS is a website development framework. In versions 5.0.0 before 5.3.2 and 5.4.0 before 5.4.2, the widget-area entity serializes widgets only when the submitted value is an array, allowing a string submitted through the admin JSON API to be stored unchanged. Entity reads, including front-end rendering and API responses, deserialize the stored value with unserialize() without an allowed_classes restriction, accepting both raw and base64-encoded serialized data. An administrator, or an attacker who obtains widget-write capability through a separate vulnerability such as chained XSS, can plant an object graph that subsequently triggers on unauthenticated page requests. Two demonstrated gadget chains in the default dependency set use composer/composer ProcessExecutor::startJob() with Process::fromShellCommandline(), or logiscape/mcp-sdk-php StdioTransport::connect() with StdioServerParameters, to reach proc_open() and execute commands as the web-server user. Deserialization bypasses constructor-based readonly safeguards, and the stored payload can execute repeatedly until the database row is repaired. Unauthenticated page access is a trigger after privileged payload storage, not an unauthenticated means of initially planting the payload. This issue has been patched in versions 5.3.2 and 5.4.2.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-114624 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114624 is a high-severity vulnerability in baserproject basercms, published on 23 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114624 exists.

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

## Sources

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

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