Security readout for executives and security teams
Plain-English summary
CVE-2018-25114 lets an unauthenticated internet user turn an exposed osCommerce 2.3.4.1 installer into server-side code execution. If the installer directory remains reachable after setup, the attacker can alter application configuration that later runs as PHP. This is a full compromise risk for affected storefront servers.
Executive priority
Treat confirmed exposure as urgent because compromise can lead to server takeover and ecommerce data impact. Prioritize public storefronts running osCommerce 2.3.4.1 with reachable installer files.
Technical view
osCommerce Online Merchant 2.3.4.1 leaves the installer workflow unauthenticated when /install/ remains accessible. The vulnerable install_4.php flow accepts crafted configuration input and can write PHP into configure.php. Because the application later includes that file, injected code executes in the web server context.
Likely exposure
Exposure is most likely on legacy osCommerce 2.3.4.1 deployments where the installation directory is still publicly reachable. Public-facing ecommerce sites are the primary concern. The bundle does not establish exposure for other osCommerce versions.
Exploitation context
Public exploit references exist, including Exploit-DB and a Metasploit module. The source bundle does not show CISA KEV listing or confirmed active exploitation, so active exploitation should not be asserted from these sources alone.
Researcher notes
The evidence supports unauthenticated configuration-file PHP injection in osCommerce 2.3.4.1. Remediation specifics beyond removing or restricting the installer are not fully detailed in the provided sources; verify vendor-supported upgrade guidance before prescribing a version fix.
Mitigation direction
- Remove or disable the osCommerce /install/ directory after installation.
- Restrict any remaining installer paths from public internet access.
- Review configure.php for unauthorized PHP or unexpected configuration changes.
- Check osCommerce guidance for supported versions, patches, or upgrade direction.
- Restore affected files from trusted backups if tampering is found.
Validation and detection
- Inventory internet-facing osCommerce deployments and confirm exact version 2.3.4.1 status.
- Verify installer paths are not reachable without authentication.
- Inspect configure.php files for unexpected executable content or recent modification times.
- Review web logs for unauthenticated installer access attempts.
- Confirm file permissions prevent the web process from changing configuration unnecessarily.
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.
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.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process 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.
Open ATT&CK lookupExecution 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-2018-25114 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
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
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 vector scores
1 official scoreWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.exploit-db.com/exploits/44374CVE reference · exploit
- https://www.oscommerce.com/CVE reference · product
- https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/multi/http/oscommerce_installer_unauth_code_exec.rbCVE reference · exploit
- https://www.vulncheck.com/advisories/oscommerce-installer-unauth-config-file-injection-php-code-executionCVE reference · third-party-advisory
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.
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.