How severe is CVE-2006-2571?

No CVSS score has been assigned to CVE-2006-2571 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2006-2571?

CVE-2006-2571 affects the following packages: org.opencms:opencms-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2006-2571?

Update org.opencms:opencms-core to 6.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2006-2571 is resolved across your whole dependency graph.

How do I detect CVE-2006-2571 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 CVE-2006-2571 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 CVE-2006-2571 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2006-2571, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2006-2571?

CVE-2006-2571 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 72th 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 CVE-2006-2571 published, and has it been updated?

CVE-2006-2571 was published on May 1, 2022 and was last updated on June 20, 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

CVE-2006-2571 — opencms-core

Fix: alkacon/opencms-core@9c7389a

CVE-2006-2571 is a security vulnerability in org.opencms:opencms-core. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.opencms:opencms-core — see the affected versions and patch details below.

Alkacon OpenCms XSS via query parameter in a search action

Published

May 1, 2022

Updated

Jun 20, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk

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

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 (XSS) vulnerability in search.html in Alkacon OpenCms 6.0.0, 6.0.2, and 6.0.3 allows remote attackers to inject arbitrary web script or HTML via the query parameter in a search action.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.opencms:opencms-core`	≥ 6.0.0&&< 6.0.4	6.0.4`org.opencms:opencms-core:6.0.4`

Affected Products

1 product · 3 configurations

Application

opencmsalkacon

3 versions

6.0.06.0.26.0.3

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Cross-site scripting (XSS) vulnerability in search.html in Alkacon OpenC…

eazel.esNVDOct 2018

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.
Fix
Update org.opencms:opencms-core to 6.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2006-2571 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.