How severe is GHSA-q7qq-9gx2-ggxv?

No CVSS score has been assigned to GHSA-q7qq-9gx2-ggxv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q7qq-9gx2-ggxv?

GHSA-q7qq-9gx2-ggxv affects the following packages: phpxmlrpc/phpxmlrpc (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-q7qq-9gx2-ggxv?

Update phpxmlrpc/phpxmlrpc to 4.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q7qq-9gx2-ggxv is resolved across your whole dependency graph.

How do I detect GHSA-q7qq-9gx2-ggxv 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-q7qq-9gx2-ggxv 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.

Is GHSA-q7qq-9gx2-ggxv actively exploited in the wild?

No public exploit code has been indexed for GHSA-q7qq-9gx2-ggxv 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-q7qq-9gx2-ggxv published, and has it been updated?

GHSA-q7qq-9gx2-ggxv was published on December 2, 2022 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

phpxmlrpc vulnerable to argument injectionGHSA-q7qq-9gx2-ggxv

GHSA-q7qq-9gx2-ggxv is a security vulnerability in phpxmlrpc/phpxmlrpc. A fix is available for phpxmlrpc/phpxmlrpc — see the affected versions and patch details below.

Published

Dec 2, 2022

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

phpxmlrpc vulnerable to argument injection via local file access in Client:send via manipulation of $protocol argument.

Affected Packages

1 total 1 fixed

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

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.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q7qq-9gx2-ggxv 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.

Frequently Asked Questions

phpxmlrpc vulnerable to argument injection via local file access in `Client:send` via manipulation of `$protocol` argument.

O3 Security · Impact-Aware SCA

Is GHSA-q7qq-9gx2-ggxv in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works