# GHSA-3fgr-xjr6-xqm8: code injection in phpxmlrpc/phpxmlrpc

> Attackers can inject code via the client argument to access local files or connect to malicious URLs in the phpxmlrpc library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Nov 2022

## What is GHSA-3fgr-xjr6-xqm8?

GHSA-3fgr-xjr6-xqm8 is a code injection vulnerability in phpxmlrpc/phpxmlrpc, published on 28 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

code injection in `Wrapper::buildClientWrapperCode` via manipulation of the `$client` argument. It was possible to force the client to access local files or connect to undesired urls instead of the intended target server's url.

## Which versions are affected by GHSA-3fgr-xjr6-xqm8?

2 open source packages ship an affected version, including phpxmlrpc/phpxmlrpc.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `phpxmlrpc/phpxmlrpc` | Packagist | All versions | 4.9.0 |
| `phpxmlrpc/phpxmlrpc` | Packagist | All versions | 4.9.0 |

## How do I fix GHSA-3fgr-xjr6-xqm8?

Upgrade phpxmlrpc/phpxmlrpc to 4.9.0 or later.

## Is GHSA-3fgr-xjr6-xqm8 being exploited?

There is no known exploitation of GHSA-3fgr-xjr6-xqm8 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-3fgr-xjr6-xqm8 and fix it if it is affected.

What it is: GHSA-3fgr-xjr6-xqm8 is a code injection vulnerability in phpxmlrpc/phpxmlrpc, published on 28 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-3fgr-xjr6-xqm8 in the wild and no public exploit code.

Affected packages and fixed versions:
- phpxmlrpc/phpxmlrpc (Packagist): affected all versions; fixed in 4.9.0
- phpxmlrpc/phpxmlrpc (Packagist): affected all versions; fixed in 4.9.0

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/GHSA-3fgr-xjr6-xqm8/ (Markdown: https://insights.sbomify.com/GHSA-3fgr-xjr6-xqm8/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-3fgr-xjr6-xqm8

---
From sbomify Insights: https://insights.sbomify.com/GHSA-3fgr-xjr6-xqm8/
Summaries are generated and may contain mistakes; the official description above is the record.