Skip to content
Fencer Intel
medium 4.3

CVE-2010-4480 json

error.php in PhpMyAdmin 3.3.8.1, and other versions before 3.4.0-beta1, allows remote attackers to conduct cross-site scripting (XSS) attac…

published 15y ago modified 4mo ago also EUVD-2010-4448

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.8%
EPSS 5.8% chance of exploitation in 30 days, percentile 93%
public exploits
1
Exploit-DB

Summary

error.php in PhpMyAdmin 3.3.8.1, and other versions before 3.4.0-beta1, allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted BBcode tag containing "@" characters, as demonstrated using "[a@url@page]".

Patch / fix

  • phpmyadmin Debian 14, Debian 13, Debian 12 4:3.3.7-3

debian advisories DEBIAN-CVE-2010-4480

Is CVE-2010-4480 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-4480 updated cvss 4.3

phpMyAdmin: XSS vulnerability via crafted BBCode tag in error.php

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (EDB-15699)
  2. Published

Exploit prediction

5.83% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-15699 phpMyAdmin - Client-Side Code Injection / Redirect Link Falsification webapps, 2010-12-06

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.