# CVE-2025-4218: handrew browserpilot gpt_selenium_agent.py GPTSeleniumAgent code injection

> Local attackers can execute arbitrary code via the instructions argument in the GPTSeleniumAgent function of the browserpilot library.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2025
- **Updated:** 5 May 2025
- **Also known as:** GHSA-m6jr-jq3q-3pp7

## What is CVE-2025-4218?

CVE-2025-4218 is a medium-severity code injection vulnerability in handrew browserpilot, published on 2 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in handrew browserpilot up to 0.2.51. It has been declared as critical. Affected by this vulnerability is the function GPTSeleniumAgent of the file browserpilot/browserpilot/agents/gpt_selenium_agent.py. The manipulation of the argument instructions leads to code injection. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2025-4218?

It affects 1 product.


Products: Andrewhhan Browserpilot.

## How do I fix CVE-2025-4218?

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

## Is CVE-2025-4218 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4218 and fix it if it is affected.

What it is: CVE-2025-4218 is a medium-severity code injection vulnerability in handrew browserpilot, published on 2 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4218 exists.

Affected product: handrew browserpilot. 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-2025-4218/ (Markdown: https://insights.sbomify.com/CVE-2025-4218/index.md)
```

## Sources

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

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