How severe is GHSA-h75c-f2xx-9vxv?

No CVSS score has been assigned to GHSA-h75c-f2xx-9vxv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h75c-f2xx-9vxv?

GHSA-h75c-f2xx-9vxv affects the following packages: org.opencms:opencms-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-h75c-f2xx-9vxv?

No patched version of org.opencms:opencms-core has shipped for GHSA-h75c-f2xx-9vxv yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-h75c-f2xx-9vxv in my Maven dependencies?

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

How do I mitigate GHSA-h75c-f2xx-9vxv 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-h75c-f2xx-9vxv?

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

Is GHSA-h75c-f2xx-9vxv actively exploited in the wild?

No public exploit code has been indexed for GHSA-h75c-f2xx-9vxv 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-h75c-f2xx-9vxv?

GHSA-h75c-f2xx-9vxv has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 26th 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-h75c-f2xx-9vxv published, and has it been updated?

GHSA-h75c-f2xx-9vxv was published on April 21, 2025 and was last updated on April 21, 2025. 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-h75c-f2xx-9vxv — opencms-core

GHSA-h75c-f2xx-9vxv is a security vulnerability in org.opencms:opencms-core. No vendor fix is recorded yet; mitigation options are listed below.

OpenCMS Cross-Site Scripting vulnerability

Also known asCVE-2024-42699

Published

Apr 21, 2025

Updated

Apr 21, 2025

Affected

1 pkg

Patched

None yet

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-h75c-f2xx-9vxv.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs26th percentile — riskier than 26% 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.opencms:opencms-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

Cross Site Scripting vulnerability in Create/Modify article function in Alkacon OpenCMS 17.0 allows remote attacker to inject javascript payload via image title sub-field in the image field

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.opencms:opencms-core`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opencms:opencms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of org.opencms:opencms-core has shipped for GHSA-h75c-f2xx-9vxv yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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-h75c-f2xx-9vxv can be triaged on real exposure rather than presence alone.

Tailored to GHSA-h75c-f2xx-9vxv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Cross Site Scripting vulnerability in Create/Modify article function in Alkacon OpenCMS 17.0 allows remote attacker to inject javascript payload via image title sub-field in the image field

O3 Security · Impact-Aware SCA

Is GHSA-h75c-f2xx-9vxv in your dependencies?

O3 Security finds GHSA-h75c-f2xx-9vxv 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