Security readout for executives and security teams
Plain-English summary
Web File Explorer 3.1 has a flaw that can let a remote attacker create executable files through the application and run code on the server. If this legacy product is exposed, the business risk is server compromise, not just file tampering.
Executive priority
Prioritize quickly if this software is present, because the described impact is remote code execution on the hosting server. If the product is not deployed, no action is needed beyond recording the negative inventory result.
Technical view
The source describes body.asp in Web File Explorer 3.1 allowing remote arbitrary file creation and code execution through the savefile action when the file parameter uses an executable extension. No CVSS, CWE, vendor CPE, or confirmed patch details are provided in the bundle.
Likely exposure
Exposure is likely limited to environments still running Web File Explorer 3.1, especially internet-facing ASP/IIS deployments. The provided data does not identify a vendor, supported versions, CPEs, or broader product family impact.
Exploitation context
The bundle includes an Exploit-DB reference, indicating public exploit information exists. It is not listed as CISA KEV, and the supplied sources do not establish active exploitation in the wild.
Researcher notes
Evidence is sparse: the CVE record names Web File Explorer 3.1 and body.asp behavior, with IBM X-Force and Exploit-DB references. Do not infer impact to other versions or products without confirming the exact code path and deployment.
Mitigation direction
- Inventory systems for Web File Explorer 3.1 or body.asp exposure.
- Remove or replace unsupported Web File Explorer deployments where possible.
- Check vendor or maintainer guidance before assuming a patch exists.
- Restrict network access to any remaining instance immediately.
- Disable executable file creation through the application if supported.
- Monitor web directories for unexpected executable files.
Validation and detection
- Confirm whether Web File Explorer 3.1 is installed or reachable.
- Review web logs for requests involving body.asp and savefile.
- Inspect application directories for newly created executable files.
- Verify internet-facing exposure through asset inventory and web scans.
- Document whether any compensating controls restrict file writes or execution.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
Execution behavior lookup
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.
Open ATT&CK lookupCVE-2009-1314 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- webfileexplorer-body-code-execution(50389)CVE reference · vdb-entry, x_refsource_XF
- 8382CVE reference · exploit, x_refsource_EXPLOIT-DB
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.