How severe is GHSA-38rq-rh9w-cmw6?

No CVSS score has been assigned to GHSA-38rq-rh9w-cmw6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-38rq-rh9w-cmw6?

GHSA-38rq-rh9w-cmw6 affects the following packages: org.craftercms:crafter-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-38rq-rh9w-cmw6?

Update org.craftercms:crafter-core to 3.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-38rq-rh9w-cmw6 is resolved across your whole dependency graph.

How do I detect GHSA-38rq-rh9w-cmw6 in my Maven dependencies?

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

How do I mitigate GHSA-38rq-rh9w-cmw6 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-38rq-rh9w-cmw6?

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

Is GHSA-38rq-rh9w-cmw6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-38rq-rh9w-cmw6 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-38rq-rh9w-cmw6?

GHSA-38rq-rh9w-cmw6 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 53th 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-38rq-rh9w-cmw6?

GHSA-38rq-rh9w-cmw6 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-38rq-rh9w-cmw6 published, and has it been updated?

GHSA-38rq-rh9w-cmw6 was published on May 24, 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.

☕ Maven

Not in CISA KEV

GHSA-38rq-rh9w-cmw6 — crafter-core

GHSA-38rq-rh9w-cmw6 is a Cross-site Scripting (XSS) vulnerability in org.craftercms:crafter-core. A fix is available for org.craftercms:crafter-core — see the affected versions and patch details below.

Cross site scripting in Crafter CMS

Also known asCVE-2017-15682

Published

May 24, 2022

Updated

Dec 7, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs53th percentile — riskier than 53% of all scored CVEsHighest risk

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.

Real-World Exposure

1 pkg affected

☕org.craftercms:crafter-core

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

In Crafter CMS Crafter Studio 3.0.1 an unauthenticated attacker is able to inject malicious JavaScript code resulting in a stored/blind XSS in the admin panel.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.craftercms:crafter-core`	≥ 3.0.0&&< 3.0.1	3.0.1`org.craftercms:crafter-core:3.0.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.craftercms:crafter-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.craftercms:crafter-core to 3.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-38rq-rh9w-cmw6 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-38rq-rh9w-cmw6 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-38rq-rh9w-cmw6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Crafter CMS Crafter Studio 3.0.1 an unauthenticated attacker is able to inject malicious JavaScript code resulting in a stored/blind XSS in the admin panel.

O3 Security · Impact-Aware SCA

Is GHSA-38rq-rh9w-cmw6 in your dependencies?

O3 Security finds GHSA-38rq-rh9w-cmw6 across Maven 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