Security readout for executives and security teams
Plain-English summary
MiniCMS 1.10 can disclose the server’s filesystem path when mc-admin/post-edit.php receives a modified id field. This does not show direct code execution or data theft in the provided sources, but it can expose internal deployment details that help attackers plan follow-on attacks.
Executive priority
Treat this as a low-urgency hardening issue unless MiniCMS 1.10 is internet-facing or part of a sensitive environment. The main business risk is information leakage that may support broader attacks.
Technical view
The CVE record describes a full path disclosure issue in mc-admin/post-edit.php in MiniCMS 1.10 triggered through a modified id field. The source bundle provides no CVSS score, CWE mapping, patch version, or confirmed exploitation details.
Likely exposure
Exposure is likely limited to sites running MiniCMS 1.10, especially where the mc-admin area is reachable by untrusted users or insufficiently access-controlled.
Exploitation context
The source bundle does not show active exploitation, and the CVE is not listed as KEV. Public evidence only supports path disclosure, not authentication bypass, code execution, or data compromise.
Researcher notes
Evidence is sparse: one CVE description and a GitHub issue reference. Do not infer broader MiniCMS versions, exploit maturity, or remediation status without additional vendor or repository confirmation.
Mitigation direction
- Confirm whether MiniCMS 1.10 is still deployed anywhere.
- Check upstream MiniCMS guidance and release history for a fix.
- Restrict mc-admin access to trusted administrators and networks.
- Migrate unsupported or unmaintained MiniCMS deployments where feasible.
- Avoid exposing verbose PHP errors in production.
Validation and detection
- Inventory public and internal web properties for MiniCMS 1.10.
- Verify whether mc-admin/post-edit.php is reachable from untrusted networks.
- Review web logs for unusual post-edit requests with altered id values.
- Confirm production error handling does not reveal filesystem paths.
- Document whether upstream provides a fixed release or workaround.
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.
CVE-2018-10424 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
- https://github.com/bg5sbk/MiniCMS/issues/18CVE reference · x_refsource_MISC
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.