How severe is CVE-2009-3821?

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

Which packages are affected by CVE-2009-3821?

CVE-2009-3821 affects the following packages: apache-solr-for-typo3/solr (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2009-3821?

Update apache-solr-for-typo3/solr to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-3821 is resolved across your whole dependency graph.

How do I detect CVE-2009-3821 in my Packagist dependencies?

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

How do I mitigate CVE-2009-3821 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-2009-3821 actively exploited in the wild?

No public exploit code has been indexed for CVE-2009-3821 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 CVE-2009-3821?

CVE-2009-3821 has an EPSS (Exploit Prediction Scoring System) score of 2.0%, placing it in the 81th 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 CVE-2009-3821?

CVE-2009-3821 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 CVE-2009-3821 published, and has it been updated?

CVE-2009-3821 was published on May 2, 2022 and was last updated on February 8, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2009-3821 — solr

Fix: TYPO3-Solr/ext-solr@5192f48

CVE-2009-3821 is a Cross-site Scripting (XSS) vulnerability in apache-solr-for-typo3/solr. A fix is available for apache-solr-for-typo3/solr — see the affected versions and patch details below.

Apache Solr Search for TYPO3 vulnerable to Cross-site Scripting

Published

May 2, 2022

Updated

Feb 8, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐘apache-solr-for-typo3/solr

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

Cross-site scripting (XSS) vulnerability in the Apache Solr Search (solr) extension 1.0.0 for TYPO3 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`apache-solr-for-typo3/solr`	all versions	1.0.1`composer require apache-solr-for-typo3/solr:^1.0.1`

Affected Products

1 product · 1 configurations

Application

solrapache

1 version

1.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for apache-solr-for-typo3/solr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update apache-solr-for-typo3/solr to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-3821 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

Cross-site scripting (XSS) vulnerability in the Apache Solr Search (solr) extension 1.0.0 for TYPO3 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

O3 Security · Impact-Aware SCA

Is CVE-2009-3821 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works