# CVE-2018-1000059: Deserialization in n/a

> Remote attackers can execute system commands and read files via PHP object injection in ValidFormBuilder.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/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:** 9 Feb 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-p9vx-hjr4-hvx2

## What is CVE-2018-1000059?

CVE-2018-1000059 is a critical unsafe deserialization vulnerability in n/a, published on 9 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ValidFormBuilder version 4.5.4 contains a PHP Object Injection vulnerability in Valid Form unserialize method that can result in Possible to execute unauthorised system commands remotely and disclose file contents in file system.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2018-1000059?

It affects 1 product.


Products: Validformbuilder Validform Builder.

## How do I fix CVE-2018-1000059?

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

## Is CVE-2018-1000059 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1000059 and fix it if it is affected.

What it is: CVE-2018-1000059 is a critical unsafe deserialization vulnerability in n/a, published on 9 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1000059 in the wild and no public exploit code.

Affected product: n/a. 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-2018-1000059/ (Markdown: https://insights.sbomify.com/CVE-2018-1000059/index.md)
```

## Sources

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

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