An unrestricted file upload vulnerability exists in Simple E-Document versions 3.0 to 3.1 that allows an unauthenticated attacker to bypass authentication by sending a specific cookie header (access=3) with HTTP requests. The application’s upload mechanism fails to restrict file types and does not validate or sanitize user-supplied input, allowing attackers to upload malicious .php scripts. Authentication can be bypassed entirely by supplying a specially crafted cookie (access=3), granting access to the upload functionality without valid credentials. If file uploads are enabled on the server, the attacker can upload a web shell and gain remote code execution with the privileges of the web server user, potentially leading to full system compromise.
Security readout for executives and security teams
Plain-English summary
Simple E-Document has a critical upload weakness that can let an unauthenticated attacker reach upload functionality and run attacker-supplied server-side code. If an exposed instance allows uploads, compromise could give the attacker the web server user's privileges. Public exploit references exist, but the provided sources do not show confirmed active exploitation.
Executive priority
Prioritize this as an urgent exposure-reduction item for any live Simple E-Document system. Public exploit references and unauthenticated remote code execution make internet-facing instances high business risk, even without confirmed KEV activity.
Technical view
CVE-2014-125126 combines missing authentication enforcement with unrestricted file upload in Simple E-Document. The CVE describes authentication bypass through a crafted cookie and acceptance of malicious PHP uploads, leading to remote code execution when uploads are enabled. CVSS v4.0 is 9.2 critical; CWE mappings include CWE-306 and CWE-434.
Likely exposure
Highest exposure is internet-facing Simple E-Document deployments, especially versions reported as 3.0 to 3.1 with upload capability enabled. The affected metadata explicitly lists version 3.0, while the description says 3.0 to 3.1, so teams should inventory both until vendor guidance clarifies scope.
Exploitation context
The source bundle links Exploit-DB and Metasploit exploit references, indicating public exploit knowledge. KEV is false, and no cited source in the bundle confirms active in-the-wild exploitation. Treat internet exposure as urgent because the described attack requires no valid credentials and has low complexity.
Researcher notes
Evidence supports critical RCE via authentication bypass plus unrestricted PHP upload. Do not assume a patch from the provided sources; none is named. Note the scope discrepancy: narrative says versions 3.0 to 3.1, while structured affected data lists 3.0.
Mitigation direction
Identify and remove public exposure for Simple E-Document instances.
Check vendor or project guidance for a supported fixed version.
Disable upload functionality where operationally possible.
Restrict access to trusted networks or authenticated gateways.
Prevent script execution from upload directories.
Review whether replacement is needed if no maintained fix exists.
Validation and detection
Inventory Simple E-Document installations and confirm exact versions.
Verify whether upload functionality is enabled on each instance.
Check whether instances are reachable from the internet.
Review web logs for suspicious unauthenticated upload activity.
Inspect upload directories for unexpected server-side scripts.
Confirm compensating controls block script execution in upload paths.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.