How severe is GHSA-rq6g-6g94-jfr4?

GHSA-rq6g-6g94-jfr4 has a CVSS score of 8.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-rq6g-6g94-jfr4?

GHSA-rq6g-6g94-jfr4 affects the following packages: starcitizentools/citizen-skin (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-rq6g-6g94-jfr4?

Update starcitizentools/citizen-skin to 3.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rq6g-6g94-jfr4 is resolved across your whole dependency graph.

How do I detect GHSA-rq6g-6g94-jfr4 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for starcitizentools/citizen-skin. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-rq6g-6g94-jfr4 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-rq6g-6g94-jfr4?

O3 pinpoints whether GHSA-rq6g-6g94-jfr4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-rq6g-6g94-jfr4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-rq6g-6g94-jfr4 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.

What is the EPSS score for GHSA-rq6g-6g94-jfr4?

GHSA-rq6g-6g94-jfr4 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 20th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-rq6g-6g94-jfr4 published, and has it been updated?

GHSA-rq6g-6g94-jfr4 was published on July 3, 2025 and was last updated on July 3, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-rq6g-6g94-jfr4

HIGH

starcitizentools/citizen-skin is vulnerable to Stored XSS attack in the legacy search bar through page descriptions

Also known asCVE-2025-53368

Published

Jul 3, 2025

Updated

Jul 3, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk20th percentile+0.11%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐘starcitizentools/citizen-skin

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

Summary

Page descriptions are inserted into raw HTML without proper sanitization by the Citizen skin when using the old search bar.

Details

The descriptions, which are unsanitized, are inserted as raw HTML: https://github.com/StarCitizenTools/mediawiki-skins-Citizen/blob/d4dfc3697a82948b3b9c4d44e9a273c79bc86b87/resources/skins.citizen.search/templates/TypeaheadListItem.mustache#L18

PoC

All of the reproduction methods require the command palette to be disabled via $wgCitizenEnableCommandPalette = false;. Additionally, the action API must be used as the Search Gateway via $wgCitizenSearchGateway = 'mwActionApi';.

TextExtracts as the description source

Enable the TextExtracts extension
Add $wgCitizenSearchDescriptionSource = 'textextracts'; to your LocalSettings.php
Create a page called CitizenXSSTextExtracts and insert <img src="" onerror="alert('citizen search xss')"> into it
Open the search modal and search for CitizenXSSTextExtracts

Description2 as the description source

Enable the Description2 extension
Add $wgEnableMetaDescriptionFunctions = true; to your LocalSettings.php to enable the {{#description2:}} parser function
Add $wgCitizenSearchDescriptionSource = 'pagedescription'; to your LocalSettings.php
Create a page called CitizenXSSDescription2 and insert {{#description2:<img src="" onerror="alert('citizen search xss 2')">}} into it
Open the search modal and search for CitizenXSSDescription2

Wikibase as the description source

Note that this method is currently untested due to issues I experienced when setting up Wikibase.

Enable Wikibase client + repo in your wiki
Add $wgCitizenSearchDescriptionSource = 'wikidata'; to your LocalSettings.php
Have an item with a description like <img src="" onerror="alert('citizen search xss 3')">
Open the search modal and search for the page linked to the item

ShortDescription as the description source

Enable the ShortDescription extension
Add $wgCitizenSearchDescriptionSource = 'wikidata'; to your LocalSettings.php
Create a page called CitizenXSSDescription4 and insert {{SHORTDESC:<img src="" onerror="alert('citizen search xss 4')">}} into it
Open the search modal and search for CitizenXSSDescription4

Impact

On all wikis that use the aforementioned settings (command palette disabled or using an old release where the old search bar is still used; using the action API as the search gateway), anybody who can edit pages is able to insert XSS payloads into the DOM for other users who are searching for specific pages.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`starcitizentools/citizen-skin`	≥ 1.9.4&&< 3.4.0	3.4.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for starcitizentools/citizen-skin. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update starcitizentools/citizen-skin to 3.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rq6g-6g94-jfr4 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 pinpoints whether GHSA-rq6g-6g94-jfr4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-rq6g-6g94-jfr4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Page descriptions are inserted into raw HTML without proper sanitization by the Citizen skin when using the old search bar. ### Details The descriptions, which are unsanitized, are inserted as raw HTML: https://github.com/StarCitizenTools/mediawiki-skins-Citizen/blob/d4dfc3697a82948b3b9c4d44e9a273c79bc86b87/resources/skins.citizen.search/templates/TypeaheadListItem.mustache#L18 ### PoC All of the reproduction methods require the command palette to be disabled via `$wgCitizenEnableCommandPalette = false;`. Additionally, the action API must be used as the Search Gateway via `$w

O3 Security · Impact-Aware SCA

Is GHSA-rq6g-6g94-jfr4 in your dependencies?

O3 detects GHSA-rq6g-6g94-jfr4 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works