How severe is GHSA-3fgr-xjr6-xqm8?

No CVSS score has been assigned to GHSA-3fgr-xjr6-xqm8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3fgr-xjr6-xqm8?

GHSA-3fgr-xjr6-xqm8 affects the following packages: phpxmlrpc/phpxmlrpc (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-3fgr-xjr6-xqm8?

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

How do I detect GHSA-3fgr-xjr6-xqm8 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-3fgr-xjr6-xqm8 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-3fgr-xjr6-xqm8?

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

Is GHSA-3fgr-xjr6-xqm8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-3fgr-xjr6-xqm8 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-3fgr-xjr6-xqm8 published, and has it been updated?

GHSA-3fgr-xjr6-xqm8 was published on November 28, 2022 and was last updated on December 7, 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-3fgr-xjr6-xqm8 — phpxmlrpc/phpxmlrpc

Fix: gggeek/phpxmlrpc@cf6e605

GHSA-3fgr-xjr6-xqm8 is a security vulnerability in phpxmlrpc/phpxmlrpc. A fix is available for phpxmlrpc/phpxmlrpc — see the affected versions and patch details below.

code injection in phpxmlrpc/phpxmlrpc

Published

Nov 28, 2022

Updated

Dec 7, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 7, 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

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.

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-3fgr-xjr6-xqm8 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-3fgr-xjr6-xqm8 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-3fgr-xjr6-xqm8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-3fgr-xjr6-xqm8 in your dependencies?

O3 Security finds GHSA-3fgr-xjr6-xqm8 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