CVE-2015-3640
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 · uneditedphpMyBackupPro 2.5 and earlier does not properly escape the "." character in request parameters, which allows remote authenticated users with knowledge of a web-accessible and web-writeable directory on the target system to inject and execute arbitrary PHP scripts by injecting scripts via the path, filename, and dirs parameters to scheduled.php, and making requests to injected scripts.
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 confidencephpMyBackupPro 2.5 and earlier fails to properly escape the '.' character in request parameters (path, filename, dirs) to scheduled.php. Authenticated attackers with knowledge of a web-accessible, web-writeable directory can inject malicious PHP scripts via these parameters and execute them through HTTP requests.
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.5CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
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 phpMyBackupPro is installedLocate phpMyBackupPro files on the web server (commonly in /phpMyBackupPro, /phpmybackuppro, or similar directories under the web root). Check for a version file or examine the main index.php for a version string.Affected if The installed version is phpMyBackupPro 2.5 or earlier.
-
Verify scheduled.php is accessibleCheck if the file scheduled.php exists within the phpMyBackupPro installation directory and is accessible via HTTP (e.g., https://yoursite.com/path/to/phpMyBackupPro/scheduled.php).Affected if scheduled.php exists and is web-accessible without additional access controls beyond login.
-
Determine if authentication is enforced on scheduled.phpAttempt to access scheduled.php without credentials or verify in the application configuration that authentication is required for all scheduled.php operations.Affected if scheduled.php can be accessed or the parameters can be manipulated without requiring valid authenticated session.
-
Identify web-accessible writeable directoriesReview the web server and phpMyBackupPro configuration to identify any directories under the web root that have write permissions and are accessible via HTTP.Affected if There exists a web-accessible directory that is also writeable by the web server process.
A user is affected if phpMyBackupPro version 2.5 or earlier is installed, scheduled.php is web-accessible, and a web-accessible writeable directory exists that could be used to inject and execute malicious PHP scripts.
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 to a patched version of phpMyBackupPro. If unable to upgrade immediately, ensure strict access controls on the web server to prevent authenticated users from writing to web-accessible directories.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3640 — 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-2015-3640 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