`\n4. Save your sett"}},{"@type":"Question","name":"How severe is GHSA-62r2-gcxr-426x?","acceptedAnswer":{"@type":"Answer","text":"GHSA-62r2-gcxr-426x has a CVSS score of 4.6/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance."}},{"@type":"Question","name":"Which packages are affected by GHSA-62r2-gcxr-426x?","acceptedAnswer":{"@type":"Answer","text":"GHSA-62r2-gcxr-426x affects the following packages: starcitizentools/citizen-skin (Packagist). Ecosystems affected: Packagist."}},{"@type":"Question","name":"How do I fix GHSA-62r2-gcxr-426x?","acceptedAnswer":{"@type":"Answer","text":"Update starcitizentools/citizen-skin to 2.31.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-62r2-gcxr-426x is resolved across your whole dependency graph."}},{"@type":"Question","name":"How do I detect GHSA-62r2-gcxr-426x in my Packagist dependencies?","acceptedAnswer":{"@type":"Answer","text":"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."}},{"@type":"Question","name":"How do I mitigate GHSA-62r2-gcxr-426x if there is no patch (or I can't update yet)?","acceptedAnswer":{"@type":"Answer","text":"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."}},{"@type":"Question","name":"How does O3 Security protect against GHSA-62r2-gcxr-426x?","acceptedAnswer":{"@type":"Answer","text":"O3 pinpoints whether GHSA-62r2-gcxr-426x is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed."}},{"@type":"Question","name":"Is GHSA-62r2-gcxr-426x actively exploited in the wild?","acceptedAnswer":{"@type":"Answer","text":"No public exploit code has been indexed for GHSA-62r2-gcxr-426x 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."}},{"@type":"Question","name":"What is the EPSS score for GHSA-62r2-gcxr-426x?","acceptedAnswer":{"@type":"Answer","text":"GHSA-62r2-gcxr-426x has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 34th 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."}},{"@type":"Question","name":"What type of vulnerability is GHSA-62r2-gcxr-426x?","acceptedAnswer":{"@type":"Answer","text":"GHSA-62r2-gcxr-426x is classified as Cross-site Scripting (XSS) (CWE-79), CWE-80 (CWE-80). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure."}},{"@type":"Question","name":"When was GHSA-62r2-gcxr-426x published, and has it been updated?","acceptedAnswer":{"@type":"Answer","text":"GHSA-62r2-gcxr-426x was published on September 30, 2024 and was last updated on September 30, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting."}}]}
Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist

GHSA-62r2-gcxr-426x

MEDIUM

starcitizentools/citizen-skin vulnerable to stored, self-XSS in the "real name" field

Also known asCVE-2024-47536
Published
Sep 30, 2024
Updated
Sep 30, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk34th percentile-0.38%
0.00%0.43%0.87%1.30%0.8%0.4%Dec 25Apr 26Jun 26

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

A user with the editmyprivateinfo right or who can otherwise change their name can XSS themselves by setting their "real name" to an XSS payload.

Details

Here's the offending line: https://github.com/StarCitizenTools/mediawiki-skins-Citizen/blob/d45c3d69f30863f622f16eb40dd41d3ca943454a/includes/Components/CitizenComponentUserInfo.php#L137

This was introduced in 717d16af35b10dab04d434aefddbf991fc8c168c

PoC

  1. Login
  2. Go to Special:Preferences
  3. Set the real name field to a string like <script>alert("Admin with a propensity for self-XSSes")</script>
  4. Save your settings and use Citizen if it's not being used already

Impact

Any user who can change their name (whether it's through the editmyprivateinfo right or through other means) can add XSS payloads that trigger for themselves only.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagiststarcitizentools/citizen-skin≥ 2.6.3&&< 2.31.02.31.0

Detection & mitigation playbook

Open-source dependency

  1. 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.

  2. Fix

    Update starcitizentools/citizen-skin to 2.31.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-62r2-gcxr-426x is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-62r2-gcxr-426x 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-62r2-gcxr-426x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary A user with the `editmyprivateinfo` right or who can otherwise change their name can XSS themselves by setting their "real name" to an XSS payload. ### Details Here's the offending line: https://github.com/StarCitizenTools/mediawiki-skins-Citizen/blob/d45c3d69f30863f622f16eb40dd41d3ca943454a/includes/Components/CitizenComponentUserInfo.php#L137 This was introduced in 717d16af35b10dab04d434aefddbf991fc8c168c ### PoC 1. Login 2. Go to Special:Preferences 3. Set the real name field to a string like `<script>alert("Admin with a propensity for self-XSSes")</script>` 4. Save your sett
O3 Security · Impact-Aware SCA

Is GHSA-62r2-gcxr-426x in your dependencies?

O3 detects GHSA-62r2-gcxr-426x 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