CVE-2024-5413
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 · uneditedA vulnerability have been discovered in PhpMyBackupPro affecting version 2.3 that could allow an attacker to execute XSS through /phpmybackuppro/scheduled.php, all parameters. This vulnerabilities could allow an attacker to create a specially crafted URL and send it to a victim to retrieve their session details.
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 confidenceA cross-site scripting (XSS) vulnerability in PhpMyBackupPro v2.3 allows attackers to inject malicious scripts through URL parameters in /phpmybackuppro/scheduled.php. Attackers can craft malicious URLs that, when visited by authenticated users, execute JavaScript in their browsers to steal session cookies or other sensitive information.
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.3CVSS 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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Locate PhpMyBackupPro installationSearch the web server document root for directories named 'phpmybackuppro' or 'phpMyBackupPro'. Check common paths like /var/www/html/, /home/*/public_html/, or C:\inetpub\wwwroot\.Affected if PhpMyBackupPro is found on the system
-
Identify installed versionExamine the main PHP files or any version.php, README, or CHANGELOG files within the PhpMyBackupPro directory for a version number.Affected if The installed version is exactly 2.3
-
Verify vulnerable file existsCheck if the file /phpmybackuppro/scheduled.php exists in the web-accessible directory.Affected if The file scheduled.php exists in the phpmybackuppro directory
-
Confirm application is web-accessibleAttempt to access the scheduled.php file via HTTP/HTTPS from a browser or curl command to confirm it is reachable.Affected if The URL returns a response from the scheduled.php script
-
Check if authentication is in useReview the PhpMyBackupPro configuration to determine if user authentication is enabled. Look for config files or login enforcement.Affected if Authentication is enabled and users can log in, allowing them to be targets for the XSS attack
A user is affected if they have PhpMyBackupPro version 2.3 installed with the scheduled.php file accessible via web and authentication enabled, as this combination allows the XSS to be triggered against authenticated 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 dataImplement proper input validation and output encoding/escaping for all parameters in scheduled.php. Use context-aware escaping functions and consider implementing Content Security Policy (CSP) headers to mitigate XSS risks.
- Consultation1.0 h
- Implementation3.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,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5413 — 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-2024-5413 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