XML-RPC for PHP allows access to local files via malicious argument to the Client::send method

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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 returntype 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…

Published by the source

11 Jan 2023, 23:54 UTC

Last modified by the source

11 Jan 2023, 23:54 UTC

Source last checked

26 Oct 2026, 13:56 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-m95x-m25c-w9mp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-m95x-m25c-w9mp

Advisory: XML-RPC for PHP allows access to local files via malicious argument to the Client::send method
IDs: GHSA-m95x-m25c-w9mp
Record: https://patchnext.com/advisories/ghsa-m95x-m25c-w9mp (revision 1, source checked 26 Oct 2026, 13:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: phpxmlrpc/phpxmlrpc 4.9.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist phpxmlrpc/phpxmlrpc: affected < 4.9.0; fixed in 4.9.0

## Suggested inspection (read-only)
- Packagist phpxmlrpc/phpxmlrpc: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on phpxmlrpc/phpxmlrpc.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-m95x-m25c-w9mp (GitHub-reviewed advisory GHSA-m95x-m25c-w9mp lists affected ranges: Packagist phpxmlrpc/phpxmlrpc >=0 <4.9.0)

Commands are suggestions: review each one before running it.