# Accessibility Glossary (a21glossary) SQL injection vulnerability

Advisory record · `GHSA-mp9g-4rg9-8rcm`

- **Identifiers:** `GHSA-mp9g-4rg9-8rcm` · `CVE-2009-4803` · `PKSA-3nfb-w4m3-5nft` · `PKSA-ffmh-bxqn-114f`
- **State:** Confirmed
- **Severity:** CVSS 4.0, no score published
- **Critical:** No
- **Weakness (CWE):** [CWE-89](https://cwe.mitre.org/data/definitions/89.html)
- **Tags:** [SQL injection](https://agentprime.io/advisories/tag/sql-injection.md)
- **Published:** 2 May 2022
- **Updated:** 11 Apr 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 2 May 2022, 03:58 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `svewap/a21glossary` (Packagist): affected `<=0.4.10`; no fixed version yet
- `wapplersystems/a21glossary` (Packagist): affected `<=0.4.10`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Accessibility Glossary (a21glossary) versions 0.4.10 and earlier are affected by an SQL injection vulnerability, which the source lists for two packages: svewap/a21glossary and wapplersystems/a21glossary. The source does not describe the attack vector, so it is unclear what access an attacker needs. A successful attack could allow arbitrary SQL commands to be run. No fixed version is listed.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- Score not published, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.010, the 63rd percentile, on 22 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:27 UTC: First seen by agentprime
- 31 Oct 2026, 14:27 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mp9g-4rg9-8rcm)

## Sources

- [GitHub Advisory Database: GHSA-mp9g-4rg9-8rcm](https://github.com/advisories/GHSA-mp9g-4rg9-8rcm)
- [OSV: GHSA-mp9g-4rg9-8rcm](https://osv.dev/vulnerability/GHSA-mp9g-4rg9-8rcm)
- <https://nvd.nist.gov/vuln/detail/CVE-2009-4803>
- <https://github.com/WapplerSystems/a21glossary>
- <https://web.archive.org/web/20090822085638/http://typo3.org/teams/security/security-bulletins/typo3-sa-2009-003>
- <https://web.archive.org/web/20200228204747/http://www.securityfocus.com/bid/33997>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-mp9g-4rg9-8rcm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-mp9g-4rg9-8rcm/>. Everything for agents: <https://agentprime.io/llms.txt>.
