LiveActive security incident?Get immediate response
CVE Record

CVE-2019-13370: index.php/admin/permissions in Ignited CMS through 2017-02-19 allows CSRF to add an administrator.

index.php/admin/permissions in Ignited CMS through 2017-02-19 allows CSRF to add an administrator.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2019-13370 describes a CSRF flaw in Ignited CMS where an authenticated administrator could be tricked into adding another administrator. The source bundle does not provide CVSS, a fixed version, or confirmed exploitation. Business risk is highest for legacy Ignited CMS deployments with reachable admin panels and active administrator sessions.

Executive priority

Treat as a priority legacy-platform risk if Ignited CMS is present. The potential impact is administrator creation, but evidence is sparse and no active exploitation is cited. Prioritize inventory, exposure reduction, and vendor or fork validation before emergency action.

Technical view

The reported issue is in index.php/admin/permissions in Ignited CMS through 2017-02-19. The weakness allows cross-site request forgery to add an administrator, implying missing or ineffective request authenticity checks on that administrative action. Public evidence is limited to the CVE record and a GitHub issue reference.

Likely exposure

Exposure appears limited to Ignited CMS deployments using code through 2017-02-19, especially where the admin permissions route is reachable by authenticated administrators. The source bundle lists affected vendor/product fields as n/a, so validate against actual deployed code rather than relying on CPE matching.

Exploitation context

No CISA KEV listing is provided, and the supplied sources do not claim active exploitation. A CSRF scenario generally depends on an authenticated administrator being induced to trigger an unwanted request, but the bundle does not provide exploit details or real-world activity evidence.

Researcher notes

The CVE record is terse and lacks CVSS, CWE mapping, CPEs, and remediation detail. The most important research task is confirming the vulnerable code path, the version boundary, and whether the referenced GitHub issue identifies a specific patch or maintained branch.

Mitigation direction

  • Check Ignited CMS project guidance or issue history for an official fix.
  • Identify and retire unsupported Ignited CMS deployments where feasible.
  • Restrict admin interface access to trusted networks while assessing exposure.
  • Review maintained forks for CSRF protection on administrator creation actions.

Validation and detection

  • Inventory any Ignited CMS deployments and code provenance.
  • Confirm whether deployed code is through 2017-02-19.
  • Review index.php/admin/permissions for CSRF token validation on admin creation.
  • Check admin user creation logs for unexpected accounts.
  • Verify admin routes are not broadly reachable from untrusted networks.
Prepared
Confidence
medium
Sources
3

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.

cve · low confidence lookup

CVE-2019-13370 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.