CVE-2025-50515
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 · uneditedAn issue was discovered in phome Empirebak 2010 in ebak2008/upload/class/config.php allowing attackers to execute arbitrary code when the config file was loaded.
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 · moderate confidenceA code injection vulnerability exists in phome Empirebak 2010's config.php file (ebak2008/upload/class/config.php) that allows remote attackers to execute arbitrary PHP code by manipulating the config file content when it is loaded by the application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 Empirebak 2010 installation directorySearch the web root for the 'ebak2008' or 'Empirebak' directory structure, typically found in web-accessible pathsAffected if The ebak2008 directory exists in the web root
-
Verify vulnerable config.php existsCheck for the presence of the file at ebak2008/upload/class/config.php within the installationAffected if The file ebak2008/upload/class/config.php exists on the server
-
Inspect config.php content for PHP code execution vectorsOpen and read the config.php file, looking for any unsanitized user-controllable values being passed to eval(), preg_replace() with /e modifier, assert(), or similar functions that execute PHP codeAffected if The config.php contains code that executes arbitrary PHP content from variables without sanitization
-
Check if config directory is web-accessibleAttempt to access the config.php file via HTTP/HTTPS from the web server to confirm it can be loaded by the applicationAffected if The application loads the config.php file over HTTP and the directory is web-accessible
-
Review config.php for external manipulation abilityDetermine if the config.php file contents can be modified by external attackers through file upload features, API endpoints, or other input vectorsAffected if An attacker can modify the contents of the config.php file through any application function
A user is affected if Empirebak 2010 is installed with the ebak2008/upload/class/config.php file present and accessible, and that config file can be manipulated to inject executable PHP code.
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 dataReview and sanitize the config.php file to prevent unsafe code execution; implement proper input validation or disable PHP execution in the config directory.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50515 — 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-2025-50515 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