How severe is GHSA-7rw2-3hhp-rc46?

GHSA-7rw2-3hhp-rc46 has a CVSS score of 4.6/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-7rw2-3hhp-rc46?

GHSA-7rw2-3hhp-rc46 affects the following packages: com.yetanalytics:lrs (Maven). Ecosystems affected: Maven.

How do I fix GHSA-7rw2-3hhp-rc46?

Update com.yetanalytics:lrs to 1.2.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7rw2-3hhp-rc46 is resolved across your whole dependency graph.

How do I detect GHSA-7rw2-3hhp-rc46 in my Maven dependencies?

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

How do I mitigate GHSA-7rw2-3hhp-rc46 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-7rw2-3hhp-rc46 actively exploited in the wild?

No public exploit code has been indexed for GHSA-7rw2-3hhp-rc46 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-7rw2-3hhp-rc46?

GHSA-7rw2-3hhp-rc46 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 39th 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.

What type of vulnerability is GHSA-7rw2-3hhp-rc46?

GHSA-7rw2-3hhp-rc46 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type 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.

When was GHSA-7rw2-3hhp-rc46 published, and has it been updated?

GHSA-7rw2-3hhp-rc46 was published on February 21, 2024 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

Cross-site Scripting Vulnerability in Statement BrowserGHSA-7rw2-3hhp-rc46

MEDIUMFix: yetanalytics/lrs@d7f4883

GHSA-7rw2-3hhp-rc46 is a medium-severity (CVSS 4.6) Cross-site Scripting (XSS) vulnerability in com.yetanalytics:lrs. A fix is available for com.yetanalytics:lrs — see the affected versions and patch details below.

Also known asCVE-2024-26140

Published

Feb 21, 2024

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-7rw2-3hhp-rc46.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs39th percentile — riskier than 39% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕com.yetanalytics:lrs

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A maliciously crafted xAPI statement could be used to perform script or other tag injection in the LRS Statement Browser.

Patches

The problem is patched in version 1.2.17 of the LRS library and version 0.7.5 of SQL LRS.

Workarounds

No workarounds exist, we recommend upgrading to version 1.2.17 of the library or version 0.7.5 of SQL LRS immediately.

References

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.yetanalytics:lrs`	all versions	1.2.17`com.yetanalytics:lrs:1.2.17`

Affected Products

2 products · 2 configurations

Application

lrsyetanalytics

< 1.2.17

range

Application

sql lrsyetanalytics

< 0.7.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.yetanalytics:lrs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.yetanalytics:lrs to 1.2.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7rw2-3hhp-rc46 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

### Impact A maliciously crafted xAPI statement could be used to perform script or other tag injection in the LRS Statement Browser. ### Patches The problem is patched in version 1.2.17 of the LRS library and [version 0.7.5 of SQL LRS](https://github.com/yetanalytics/lrsql/releases/tag/v0.7.5). ### Workarounds No workarounds exist, we recommend upgrading to version 1.2.17 of the library or version 0.7.5 of SQL LRS immediately. ### References * [LRS Tag](https://github.com/yetanalytics/lrs/releases/tag/v1.2.17) * [LRS lib on Clojars](https://clojars.org/com.yetanalytics/lrs/versions/1.2.17)