LiveActive security incident?Get immediate response
CVE Record

CVE-2018-19180: statics/app/index/controller/Install.php in YUNUCMS 1.1.5 (if install.lock is not present) allows remote at...

statics/app/index/controller/Install.php in YUNUCMS 1.1.5 (if install.lock is not present) allows remote attackers to execute arbitrary PHP code by placing this code in the index.php?s=index/install/setup2 DB_PREFIX field, which is written to database.php.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

YUNUCMS 1.1.5 can allow remote PHP code execution when its installer remains unlocked. The issue depends on install.lock being absent, meaning exposed or incomplete installations are the primary concern. Public sources do not provide CVSS scoring, vendor CPE data, or a confirmed patch.

Executive priority

Treat exposed YUNUCMS 1.1.5 installer instances as urgent. Prioritize internet-facing systems first, especially any deployment where installation files remain accessible or install.lock is missing.

Technical view

The CVE describes statics/app/index/controller/Install.php accepting attacker-controlled content through the installer setup2 DB_PREFIX field and writing it into database.php. If install.lock is missing, this can result in arbitrary PHP code execution. Evidence is limited to the CVE record and a GitHub issue reference.

Likely exposure

Exposure is likely limited to YUNUCMS 1.1.5 deployments where the installer is reachable from the internet and install.lock is absent. The source bundle does not identify CPEs, vendor-maintained affected ranges, or broader product lineage.

Exploitation context

CISA KEV is false, and the provided sources do not state active exploitation. The bug is still serious because the described condition enables remote code execution through an installation workflow left accessible after deployment.

Researcher notes

The public record is sparse: no CVSS, CWE, CPE, or official patch statement is included in the bundle. The core exposure condition is clear, but remediation should be confirmed against project guidance before broad claims are made.

Mitigation direction

  • Check project or vendor guidance for any fixed release or official remediation.
  • Verify install.lock exists on deployed YUNUCMS 1.1.5 systems.
  • Remove or disable public access to installation components after setup.
  • Restrict installer paths to trusted administrators only if removal is not possible.
  • Consider upgrading or replacing unsupported deployments if no maintained fix exists.

Validation and detection

  • Inventory public web assets for YUNUCMS 1.1.5 deployments.
  • Confirm whether installer routes remain reachable from untrusted networks.
  • Check the deployed filesystem for install.lock presence.
  • Review database.php for unexpected PHP content or recent unauthorized changes.
  • Review web logs for suspicious access to installer setup routes.
Prepared
Confidence
medium
Sources
3

Public sources used

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.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-19180 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.