Security readout for executives and security teams
Plain-English summary
GreenCMS v2.3.0603 has a reported CSRF issue that can make an authenticated administrator’s browser trigger deletion of a log file. The documented impact is loss of log data, not system takeover or data theft. Severity and affected-product metadata are incomplete in the provided sources.
Executive priority
Treat this as a targeted hygiene issue for any remaining GreenCMS deployment. It is not documented as actively exploited, but log deletion can weaken forensic visibility and compliance evidence after other incidents.
Technical view
The CVE describes a cross-site request forgery weakness in GreenCMS v2.3.0603 affecting the admin clear-log action at index.php?m=admin&c=data&a=clear. A remote attacker would need to induce a privileged session to make the state-changing request. No CVSS, CWE, official fix, or exploitation evidence is provided.
Likely exposure
Exposure is limited to environments still running GreenCMS v2.3.0603, especially where admin users access the application from browsers that could be targeted. The provided affected-product fields are listed as n/a, so asset confirmation is required.
Exploitation context
The source bundle does not show KEV listing or active exploitation. The reported scenario is CSRF against an administrative function that deletes logs, which could impair auditing and incident review if an administrator is tricked into triggering it.
Researcher notes
Evidence is sparse: one CVE description and a GitHub issue reference. The CVE does not provide CVSS, CWE mapping, patch information, or a vendor advisory. Avoid assuming broader product impact beyond GreenCMS v2.3.0603.
Mitigation direction
- Identify any GreenCMS v2.3.0603 instances in production or legacy environments.
- Check GreenCMS project guidance for a fixed version or recommended mitigation.
- Restrict administrative access to trusted networks or VPN where feasible.
- Require administrators to use separate, hardened sessions for CMS administration.
- Preserve web and application logs outside the CMS-controlled path.
Validation and detection
- Confirm deployed GreenCMS versions and whether v2.3.0603 is present.
- Review the admin clear-log action for anti-CSRF protections.
- Check whether admin routes are reachable from untrusted networks.
- Review logs for unexpected clear-log activity or audit gaps.
- Confirm log retention is independent of the CMS application.
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-19376 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/GreenCMS/GreenCMS/issues/114CVE 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.