# GHSA-m95x-m25c-w9mp: XML-RPC for PHP allows access to local files via malicious argument to the Client::send method

> Attackers can force the XML-RPC client to access local files or connect to arbitrary URLs via malicious arguments, leading to data exposure or SSRF.

- **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:** 11 Jan 2023

## What is GHSA-m95x-m25c-w9mp?

GHSA-m95x-m25c-w9mp is a server-side request forgery vulnerability in phpxmlrpc/phpxmlrpc, published on 11 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Abusing the `$method` argument of Client::send, it was possible to force the client to _access local files_ or _connect to undesired urls_ instead of the intended target server's url (the one used in the Client constructor).

This weakness only affects installations where all the following conditions apply, at the same time:

- the xmlrpc Client is used, ie. not xmlrpc servers
- untrusted data (eg. data from remote users) is used as value for the `$method` argument of method `Client::send()`, in conjunction with conditions which trigger usage of curl as http transport (ie. either using the https, http11 or http2 protocols, or calling `Client::setUseCurl()` beforehand)
- either have set the Clients `return_type` property to 'xml', or make the resulting Response's object `httpResponse` member, which is intended to be used for debugging purposes only, available to 3rd parties, eg. by displaying it to the end user or serializing it in some storage (note that the same data can also be accessed via magic property `Response::raw_data`, and in the Request's `httpResponse` member)

This is most likely a very uncommon usage scenario, and as such the chances of exploitation of this issue may be low.

If it is not possible to upgrade to this release of the library at this time, a proactive security measure, to avoid the Client accessing any local file on the server which hosts it, is to add the following call to your code:

      $client->setCurlOptions([CURLOPT_PROTOCOLS, CURLPROTO_HTTPS|CURLPROTO_HTTP]);

Originally reported as issue #81

## Which versions are affected by GHSA-m95x-m25c-w9mp?

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-m95x-m25c-w9mp?

Upgrade phpxmlrpc/phpxmlrpc to 4.9.0 or later.

## Is GHSA-m95x-m25c-w9mp being exploited?

There is no known exploitation of GHSA-m95x-m25c-w9mp in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-m95x-m25c-w9mp and fix it if it is affected.

What it is: GHSA-m95x-m25c-w9mp is a server-side request forgery vulnerability in phpxmlrpc/phpxmlrpc, published on 11 Jan 2023. 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-m95x-m25c-w9mp 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-m95x-m25c-w9mp/ (Markdown: https://insights.sbomify.com/GHSA-m95x-m25c-w9mp/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-m95x-m25c-w9mp

---
From sbomify Insights: https://insights.sbomify.com/GHSA-m95x-m25c-w9mp/
Summaries are generated and may contain mistakes; the official description above is the record.