Versions preceding 0.6.1 of the phpxmlrpc/extras project are susceptible to a Cross-Site Scripting (XSS) vulnerability. This vulnerability exists within the class documenting_xmlrpc_server when processing the GET methodName parameter.
Vendor
phpxmlrpc vulnerabilities
6 published CVES affecting phpxmlrpc, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 0
- High
- 0
- Medium
- 1
- Low
- 0
- Unscored
- 5
- CISA KEV
- 0
Products
Latest phpxmlrpc CVEs
Newest publication first
-
MediumCVSS 6.1
-
Unknown
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 follow...
-
Unknown
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...
-
Unknown
The bundled xml-rpc debugger is susceptible to XSS attacks. Since the debugger is not designed to be exposed to end users but only to the developers using this library, and in the default configuration it is not exposed to requests from the web, the likelihood of exploitation may...
-
Unknown
phpxmlrpc vulnerable to argument injection via local file access in Client:send via manipulation of $protocol argument.
-
Unknown
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.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.