CVE-2007-2245
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple cross-site scripting (XSS) vulnerabilities in phpMyAdmin before 2.10.1.0 allow remote attackers to inject arbitrary web script or HTML via (1) the fieldkey parameter to browse_foreigners.php or (2) certain input to the PMA_sanitize function.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCross-site scripting (XSS) vulnerabilities in phpMyAdmin versions before 2.10.1.0 allow remote attackers to inject arbitrary web script or HTML via the fieldkey parameter in browse_foreigners.php or through insufficient sanitization in the PMA_sanitize function.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.10.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm phpMyAdmin installationCheck for phpMyAdmin directories (commonly /phpMyAdmin, /phpmyadmin, /pma) or files like libraries/common.inc.php or index.php with phpMyAdmin content in the web rootAffected if phpMyAdmin files or directories are found on the server
-
Identify installed phpMyAdmin versionCheck the version file (VERSION or README) in the phpMyAdmin directory, or view the login page footer which typically displays the version numberAffected if The displayed version is below 2.10.1.0 (e.g., 2.10.0.x, 2.9.x, etc.)
-
Verify browse_foreigners.php is accessibleAttempt to access the file directly via HTTP (e.g., https://yourserver/phpmyadmin/browse_foreigners.php) or check if the file exists in the phpMyAdmin installation directoryAffected if The file exists and responds to requests without authentication errors
-
Check for unpatched PMA_sanitize functionIf source code access is available, inspect the libraries/sanitizer.inc.php or common.inc.php file for the PMA_sanitize function implementation - look for insufficient filtering of special characters in the fieldkey parameterAffected if The function lacks proper HTML entity encoding or allows script tags in the fieldkey parameter without sanitization
The environment is affected if phpMyAdmin version 2.10.1.0 or lower is installed AND browse_foreigners.php is accessible to users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade phpMyAdmin to version 2.10.1.0 or later to obtain the patched version that properly sanitizes user input in the affected parameters.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2245 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-2245 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data