How severe is GHSA-ww6p-q26w-fr6m?

GHSA-ww6p-q26w-fr6m has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-ww6p-q26w-fr6m?

GHSA-ww6p-q26w-fr6m affects the following packages: phpxmlrpc/extras (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-ww6p-q26w-fr6m?

Update phpxmlrpc/extras to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ww6p-q26w-fr6m is resolved across your whole dependency graph.

How do I detect GHSA-ww6p-q26w-fr6m in my Packagist dependencies?

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

How do I mitigate GHSA-ww6p-q26w-fr6m if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-ww6p-q26w-fr6m actively exploited in the wild?

No public exploit code has been indexed for GHSA-ww6p-q26w-fr6m 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-ww6p-q26w-fr6m published, and has it been updated?

GHSA-ww6p-q26w-fr6m was published on May 20, 2024 and was last updated on December 5, 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

MEDIUM severity

phpxmlrpc/extra XSS in class documenting_xmlrpc_serverGHSA-ww6p-q26w-fr6m

MEDIUMFix: gggeek/phpxmlrpc-extras@65c336e

GHSA-ww6p-q26w-fr6m is a medium-severity (CVSS 6.1) vulnerability in phpxmlrpc/extras. A fix is available for phpxmlrpc/extras — see the affected versions and patch details below.

Published

May 20, 2024

Updated

Dec 5, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 5, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘phpxmlrpc/extras

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

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.

Affected Packages

1 total 1 fixed

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

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phpxmlrpc/extras, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update phpxmlrpc/extras to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ww6p-q26w-fr6m is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-ww6p-q26w-fr6m in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works