Security readout for executives and security teams
Plain-English summary
MiniCMS V1.10 has a stored cross-site scripting issue in the admin post editor content box. If abused, malicious content could execute in another user's browser and expose cookies. The source bundle does not provide CVSS, patch details, or evidence of active exploitation.
Executive priority
Handle as a legacy web application risk requiring inventory and targeted remediation. It is not KEV-listed in the provided data, but stored XSS affecting cookies can still create account compromise risk.
Technical view
CVE-2019-13340 is a stored XSS in mc-admin/post-edit.php through the content box in MiniCMS V1.10. The CVE notes possible cookie theft and says it is distinct from several earlier MiniCMS XSS CVEs. No CPEs, CWE, CVSS, or fix version are provided.
Likely exposure
Exposure is most relevant to organizations still running MiniCMS V1.10, especially where post content can be created or modified by untrusted or lower-privileged users. The source data lacks vendor, CPE, and deployment details.
Exploitation context
The CVE record describes potential cookie theft through stored XSS, but the bundle does not show KEV listing, active exploitation, public exploit status, or a confirmed fixed release.
Researcher notes
Evidence is sparse: one GitHub issue reference and CVE metadata. The affected product is described in the title and description, while structured affected fields are n/a. Avoid assuming patch availability or broader version impact.
Mitigation direction
- Identify any MiniCMS V1.10 deployments.
- Check the referenced GitHub issue and project guidance for fixes.
- Restrict admin and post-editing access to trusted users.
- Review content sanitization and output encoding before continued use.
- Consider upgrading or replacing MiniCMS if no maintained fix exists.
Validation and detection
- Confirm whether MiniCMS V1.10 is present.
- Review mc-admin/post-edit.php exposure and access controls.
- Check post content history for unexpected script-like content.
- Review logs for suspicious post edits or admin sessions.
- Verify any remediation against vendor or project guidance.
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-2019-13340 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/32CVE 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.