CVE-2025-12867
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 · uneditedEIP Plus developed by Hundred Plus has an Arbitrary File Uplaod vulnerability, allowing privileged remote attackers to upload and execute web shell backdoors, thereby enabling arbitrary code execution on the server.
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 confidenceEIP Plus contains an arbitrary file upload vulnerability allowing authenticated, privileged remote attackers to upload malicious files including web shells to the server. By executing these uploaded files, attackers can achieve arbitrary code execution on the underlying system.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Identify if EIP Plus is installedSearch for EIP Plus installation directories, check running processes for EIP Plus services, or query application listings on the serverAffected if EIP Plus software is present on the system
-
Check if file upload functionality is enabledLocate the file upload endpoint or module in the EIP Plus web application; review configuration files for upload capability settingsAffected if File upload functionality is accessible and not disabled
-
Verify authentication controls on upload endpointsReview access control lists, session management configuration, and upload endpoint permission settings to confirm privileged user requirementsAffected if Upload endpoints allow access without proper privileged authentication or enforce weak authorization
-
Inspect upload directory for execute permissionsExamine the web server configuration and file system permissions on the designated upload directory to determine if uploaded files can be executed as scriptsAffected if Upload directory is located within a web-accessible path and permits execution of uploaded content
-
Scan for unexpected uploaded filesSearch upload directories for suspicious file extensions (.php, .asp, .jsp, .exe, .sh) or recently created executable files that do not match expected upload patternsAffected if Unknown or malicious file types exist in upload directories, especially web shell patterns
You are affected if EIP Plus is running with file upload functionality accessible to authenticated privileged users and the upload directory is web-accessible with execute permissions.
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 file upload validation including magic byte verification, restrict upload directory to prevent execution (non-executable web root), rename uploaded files to safe names, and enforce proper authentication/authorization on upload endpoints.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12867 — 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-12867 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