CVE-2025-50002
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in Farost Energia energia allows Upload a Web Shell to a Web Server.This issue affects Energia: from n/a through <= 1.1.2.
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 confidenceFarost Energia energia web application has an unrestricted file upload vulnerability that allows attackers to upload web shell scripts to the server, enabling full remote code execution. The lack of proper file type validation and content inspection on upload functionality permits dangerous file types to be stored and executed.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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.
-
Identify Farost Energia installationLocate the web application files and determine if Farost Energia energia is present in your environment. Search for application directories or check web server configurations for this application.Affected if Farost Energia energia web application is installed
-
Locate upload functionalitySearch the application for file upload endpoints, forms, or API paths that handle file uploads. Common indicators include multipart form submissions, file input fields, or upload API routes.Affected if The application contains file upload functionality
-
Verify file type validation existsExamine the upload handling code for server-side validation that checks file types, extensions, or magic bytes before storing files. Look for allowlists, MIME type checks, or content inspection logic.Affected if No server-side file type validation or allowlist is implemented on the upload function
-
Check uploaded file storage locationIdentify where uploaded files are stored relative to the web root. Examine the file storage path configuration to determine if uploads reside within or outside the web-accessible directory.Affected if Uploaded files are stored inside the web root directory
-
Verify script execution is disabled in upload directoryCheck web server configuration (e.g., Apache .htaccess, Nginx config) or application settings for directives that prevent script execution (e.g., php_flag engine off, disable_functions) in the upload storage directory.Affected if Script execution is not explicitly disabled in the upload storage directory
Your environment is affected if the Farost Energia energia web application is installed with an accessible file upload feature that lacks proper server-side file type validation, stores files within the web root, and does not disable script execution in the upload directory.
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 strict allowlist-based file type validation including magic byte verification, store uploads outside the web root with non-executable extensions, and disable script execution in upload directories.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50002 — 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-50002 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