Skip to content
Noroxi
CVE-2013-4995· NVD / CVE Program· CNA mitre

Cross-site scripting (XSS) vulnerability in phpMyAdmin 3.5.x before 3.5.8.2 and 4.0.x before 4.0.4.2 allows remote authenticated users to in

Cross-site scripting (XSS) vulnerability in phpMyAdmin 3.5.x before 3.5.8.2 and 4.0.x before 4.0.4.2 allows remote authenticated users to inject arbitrary web script or HTML via a crafted SQL query that is not properly handled during the display of row information.

LowCVSS 3.5 · v2.0—No exploit Fix available
Published
Jul 31, 2013
Updated
Jun 16, 2026
EPSS
1.4% · 72th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

14

Monitor

Low priority for now.

CVSS
14 / 40 · 3.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.4%

Affected systems

VendorProduct
phpmyadminphpmyadmin

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • phpmyadmin phpmyadmin3.5.0.0
  • phpmyadmin phpmyadmin3.5.1.0
  • phpmyadmin phpmyadmin3.5.2.0
  • phpmyadmin phpmyadmin3.5.2.1
  • phpmyadmin phpmyadmin3.5.2.2
  • phpmyadmin phpmyadmin3.5.3.0
  • phpmyadmin phpmyadmin3.5.4
  • phpmyadmin phpmyadmin3.5.5
  • phpmyadmin phpmyadmin3.5.6
  • phpmyadmin phpmyadmin3.5.7
  • phpmyadmin phpmyadmin3.5.8
  • phpmyadmin phpmyadmin3.5.8.1
  • phpmyadmin phpmyadmin4.0.0
  • phpmyadmin phpmyadmin4.0.1
  • phpmyadmin phpmyadmin4.0.2
  • phpmyadmin phpmyadmin4.0.3
  • phpmyadmin phpmyadmin4.0.4
  • phpmyadmin phpmyadmin4.0.4.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12phpmyadminbefore 4:4.0.4.2-14:4.0.4.2-1
Debian:6.0phpmyadminbefore 4:3.3.7-84:3.3.7-8
Debian:7phpmyadminbefore 4:3.4.11.1-2+deb7u14:3.4.11.1-2+deb7u1
openSUSE:TumbleweedphpMyAdminbefore 4.6.5.2-1.14.6.5.2-1.1

Same product

phpmyadmin: all records

Other highest-scoring records for the same primary product.

  • CVE-2009-1151Static code injection vulnerability in setup.php in phpMyAdmin 2.11.x before 2.11.9.5 and 3.x before 3.1.3.1 allows remote attackers to injeKEV
    98Now
  • CVE-2018-12613An issue was discovered in phpMyAdmin 4.8.x before 4.8.2, in which an attacker can include (view and potentially execute) files on the serve
    65This week
  • CVE-2016-5734phpMyAdmin 4.0.x before 4.0.10.16, 4.4.x before 4.4.15.7, and 4.6.x before 4.6.3 does not properly choose delimiters to prevent use of the p
    63This week
  • CVE-2020-26935An issue was discovered in SearchController in phpMyAdmin before 4.9.6 and 5.x before 5.0.3.
    59Plan
  • CVE-2012-5159phpMyAdmin 3.5.2.2, as distributed by the cdnetworks-kr-1 mirror during an unspecified time frame in 2012, contains an externally introduced
    52Plan
  • CVE-2020-5504In phpMyAdmin 4 before 4.9.4 and 5 before 5.0.1, SQL injection exists in the user accounts page.
    47Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:phpmyadmin4:4.0.4.2-1 · Debian:12Package registry (OSV)
opensuse:phpMyAdmin4.6.5.2-1.1 · openSUSE:TumbleweedPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

    If successful

    Confidentiality
    none
    Integrity
    P · data or configuration can be modified
    Availability
    none
    Attack complexity
    M
    Confidentiality impact
    None
    Integrity impact
    P
    Availability impact
    None

    Weakness class (CWE)

    CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

    CVSS vector

    AV:N/AC:M/Au:S/C:N/I:P/A:N

    nvd-primary

    Root cause

    User content is inserted into the page as HTML. The browser interprets the content as code rather than data.

    The bug in code

    The whole CWE-79 class

    A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

    Vulnerable

    ts
    commentEl.innerHTML = comment.body;

    Fixed

    ts
    commentEl.textContent = comment.body;

    Attack context

    MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

    ATT&CK techniques

    —

    Noroxi analysis

    No Noroxi analysis for this record yet

    We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

    We use this product, ask for help

    Change log

    1. Fix✗ → ✓

    For records you follow, these changes also arrive as notifications. →

    References

    Vendor advisories and official records. Exploit/PoC links are deliberately left out.

    All records