Security readout for executives and security teams
Plain-English summary
Usermin versions before 1.660 can let a logged-in user run code on the server. That can become a full compromise because the CVSS vector shows high confidentiality, integrity, and availability impact with changed scope.
Executive priority
Treat as urgent for any internet-reachable or broadly accessible Usermin deployment. A low-privileged account may be enough to reach server-level compromise.
Technical view
The issue is in uconfig_save.cgi sig_file_free, where two-argument Perl open is used instead of the safer three-argument form. Sources describe authenticated network remote code execution in Usermin 0.980 through 1.x before 1.660.
Likely exposure
Exposure is likely where Usermin is deployed, reachable over a network, and running a version before 1.660. The bundle’s structured affected data only lists 0.980, while the description states a broader pre-1.660 range.
Exploitation context
The CVE is not listed as KEV in the bundle. The provided sources support remote code execution with low privileges required, but they do not provide evidence of active exploitation.
Researcher notes
There is a source inconsistency: narrative affected range is 0.980 through 1.x before 1.660, but structured affected data lists 0.980 only. Validate against installed versions and vendor records.
Mitigation direction
- Upgrade Usermin to 1.660 or later, following vendor guidance.
- Restrict Usermin access to trusted administrative networks.
- Review Usermin accounts and remove unnecessary access.
- Monitor CVE and vendor sources for updated remediation guidance.
Validation and detection
- Inventory Usermin servers and record exact versions.
- Prioritize any Usermin version before 1.660 for remediation.
- Confirm Usermin is not reachable from untrusted networks.
- Review logs for unexpected authenticated requests to uconfig_save.cgi.
- Retest exposure after upgrade or access-control changes.
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-96: 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-2015-2079 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.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://code-white.com/public-vulnerability-list/CVE reference
- https://code-white.com/blog/2015-05-cve-2015-2079-rce-usermin/CVE reference
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.
Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')
Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.