LiveActive security incident?Get immediate response
CVE Record

CVE-2013-3239: phpMyAdmin 3.5.x before 3.5.8 and 4.x before 4.0.0-rc3, when a SaveDir directory is configured, allows remo...

phpMyAdmin 3.5.x before 3.5.8 and 4.x before 4.0.0-rc3, when a SaveDir directory is configured, allows remote authenticated users to execute arbitrary code by using a double extension in the filename of an export file, leading to interpretation of this file as an executable file by the Apache HTTP Server, as demonstrated by a .php.sql filename.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is an old phpMyAdmin issue where an authenticated user could make an exported file run as server-side code under a specific SaveDir configuration. The business risk is highest for legacy, internet-accessible phpMyAdmin instances, because successful abuse could let the attacker run code on the web server. Exposure is likely limited to legacy phpMyAdmin deployments in the named version ranges, with SaveDir configured, and Apache handling exported files in a way that treats them as executable. Authenticated phpMyAdmin access is required according to the CVE description. Prioritize remediation if any legacy phpMyAdmin is still reachable, especially from the internet. Although the issue is old and requires authentication plus specific configuration, the impact is server-side code execution, which can become a full system compromise path. Mitigation focus: Upgrade phpMyAdmin to 3.5.8, 4.0.0-rc3, or a later vendor-supported package.; Review PMASA-2013-3 and applicable distribution advisories for package-specific remediation guidance.; Audit whether SaveDir is configured on any remaining legacy phpMyAdmin deployments..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2013-3239 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.