How severe is GHSA-pxqj-xrv5-qvjf?

No CVSS score has been assigned to GHSA-pxqj-xrv5-qvjf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pxqj-xrv5-qvjf?

GHSA-pxqj-xrv5-qvjf affects the following packages: phpxmlrpc/phpxmlrpc (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-pxqj-xrv5-qvjf?

Update phpxmlrpc/phpxmlrpc to 4.9.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pxqj-xrv5-qvjf is resolved across your whole dependency graph.

How do I detect GHSA-pxqj-xrv5-qvjf in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phpxmlrpc/phpxmlrpc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-pxqj-xrv5-qvjf if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-pxqj-xrv5-qvjf?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pxqj-xrv5-qvjf can be triaged on real exposure rather than presence alone.

Is GHSA-pxqj-xrv5-qvjf actively exploited in the wild?

No public exploit code has been indexed for GHSA-pxqj-xrv5-qvjf yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-pxqj-xrv5-qvjf published, and has it been updated?

GHSA-pxqj-xrv5-qvjf was published on January 11, 2023 and was last updated on November 28, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-pxqj-xrv5-qvjf — phpxmlrpc/phpxmlrpc

GHSA-pxqj-xrv5-qvjf is a security vulnerability in phpxmlrpc/phpxmlrpc. A fix is available for phpxmlrpc/phpxmlrpc — see the affected versions and patch details below.

XML-RPC for PHP's debugger vulnerable to possible XSS attack

Published

Jan 11, 2023

Updated

Nov 28, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 28, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘phpxmlrpc/phpxmlrpc

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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 be low.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`phpxmlrpc/phpxmlrpc`	all versions	4.9.2`composer require phpxmlrpc/phpxmlrpc:^4.9.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phpxmlrpc/phpxmlrpc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update phpxmlrpc/phpxmlrpc to 4.9.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pxqj-xrv5-qvjf is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pxqj-xrv5-qvjf can be triaged on real exposure rather than presence alone.

Tailored to GHSA-pxqj-xrv5-qvjf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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 be low.

O3 Security · Impact-Aware SCA

Is GHSA-pxqj-xrv5-qvjf in your dependencies?

O3 Security finds GHSA-pxqj-xrv5-qvjf across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works