XML-RPC for PHP's Wrapper::buildClientWrapperCode method allows code injection via malicious $client argument

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.

In order for this weakness to be exploited, the following conditions have to apply, at the same time: - method Wrapper::buildClientWrapperCode, or any methods which depend on it, such as Wrapper::wrapXmlrpcServer, Wrapper::wrapXmlrpcMethod or Wrapper::buildWrapMethodSource must be in use. Note that they are not used by default in either the Client or Server classes provided by the library; the developer has to specifically make use of them in his/her own code - the $client argument to either of those methods should have been built with malicious data, ie. data controlled by a 3rd party, passed to its constructor call This is most likely an uncommon usage scenario, and as such the chances of exploitation may be low. NB the graphical debugger which is shipped as part of the library is vulnerable to this, when used with the option "Generate stub for method call" selected. In that case, the debugger will display but not execute the malicious code, which would have to be provided via…

Published by the source

11 Jan 2023, 23:53 UTC

Last modified by the source

11 Jan 2023, 23:53 UTC

Source last checked

26 Oct 2026, 13:56 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7vcx-v65q-9wpg

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

# Patch Next advisory brief: GHSA-7vcx-v65q-9wpg

Advisory: XML-RPC for PHP's `Wrapper::buildClientWrapperCode` method allows code injection via malicious `$client` argument
IDs: GHSA-7vcx-v65q-9wpg
Record: https://patchnext.com/advisories/ghsa-7vcx-v65q-9wpg (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-7vcx-v65q-9wpg (GitHub-reviewed advisory GHSA-7vcx-v65q-9wpg lists affected ranges: Packagist phpxmlrpc/phpxmlrpc >=0 <4.9.0)

Commands are suggestions: review each one before running it.