Security readout for executives and security teams
Plain-English summary
PublicCMS V4.0.20180210 has a CSRF flaw that could let an attacker cause an administrator’s browser to create another admin account. That can turn a web-session weakness into full CMS control. The public record does not provide CVSS scoring, confirmed patch details, or evidence of active exploitation.
Executive priority
Treat this as high priority if PublicCMS V4.0.20180210 is in use, because successful abuse could create administrator access. If PublicCMS is not present, no action is needed beyond documenting non-exposure.
Technical view
The reported issue is a CSRF vulnerability affecting the PublicCMS administrative user-save flow at admin/sysUser/save.do with parameters shown in the CVE description. The stated impact is unauthorized creation of an admin account. Sources do not confirm affected version range beyond V4.0.20180210, prerequisites, or fixed release details.
Likely exposure
Exposure is most likely limited to PublicCMS V4.0.20180210 deployments where the administrative interface is reachable and administrators use active browser sessions. The sources do not identify other affected versions, products, CPEs, or hosted-service exposure.
Exploitation context
CISA KEV status is false, and the supplied sources do not show active exploitation. CSRF usually depends on an authenticated user visiting attacker-controlled content, but the public record here does not fully document prerequisites or exploit reliability.
Researcher notes
Evidence is sparse: the CVE description and GitHub issue identify the endpoint and impact, but not CVSS, CWE, affected ranges, patch status, or exploitation in the wild. Avoid assuming broader PublicCMS impact without vendor confirmation.
Mitigation direction
- Identify whether PublicCMS V4.0.20180210 is deployed anywhere.
- Check vendor issue history and release notes for fixed versions or guidance.
- Restrict PublicCMS admin access to trusted networks or VPN.
- Harden admin sessions and require reauthentication for privileged account changes.
- Review whether anti-CSRF protection exists on administrative user-save actions.
Validation and detection
- Confirm deployed PublicCMS version and administrative interface exposure.
- Review admin account lists for unknown or recently created administrators.
- Check web and application logs for sysUser/save.do account-change activity.
- Test in a controlled environment whether admin user creation requires CSRF protection.
- Document any compensating controls if no vendor fix is available.
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-11500 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/sanluan/PublicCMS/issues/11CVE 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.