How severe is CVE-2009-4803?

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

Which packages are affected by CVE-2009-4803?

CVE-2009-4803 affects the following packages: svewap/a21glossary (Packagist), wapplersystems/a21glossary (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2009-4803?

The records we use list no patched version of svewap/a21glossary for CVE-2009-4803. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

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

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

How do I mitigate CVE-2009-4803 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2009-4803 actively exploited in the wild?

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

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

CVE-2009-4803 is classified as SQL Injection (CWE-89). 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-4803 published, and has it been updated?

CVE-2009-4803 was published on May 2, 2022 and was last updated on April 11, 2025. 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-4803 — a21glossary

CVE-2009-4803 is a SQL Injection vulnerability in svewap/a21glossary. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Accessibility Glossary (a21glossary) SQL injection vulnerability

Published

May 2, 2022

Updated

Apr 11, 2025

Affected

2 pkgs

Patched

See advisory

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

🐘svewap/a21glossary🐘wapplersystems/a21glossary

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

SQL injection vulnerability in the Accessibility Glossary (a21glossary) extension 0.4.10 and earlier for TYPO3 allows remote attackers to execute arbitrary SQL commands via unspecified vectors.

Affected Packages

2 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`svewap/a21glossary`	all versions	No fix
🐘Packagist	`wapplersystems/a21glossary`	all versions	No fix

Affected Products

1 product · 5 configurations

Application

accessibility glossaryandreas_schwarzkopf

≤ 0.4.10

4 versions

0.4.00.4.70.4.80.4.9

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for svewap/a21glossary, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of svewap/a21glossary for CVE-2009-4803. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

SQL injection vulnerability in the Accessibility Glossary (a21glossary) extension 0.4.10 and earlier for TYPO3 allows remote attackers to execute arbitrary SQL commands via unspecified vectors.

O3 Security · Impact-Aware SCA

Is CVE-2009-4803 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works