LiveActive security incident?Get immediate response
CVE Record

CVE-2019-1010178: Fred MODX Revolution < 1.0.0-beta5 is affected by: Incorrect Access Control - CWE-648.

Fred MODX Revolution < 1.0.0-beta5 is affected by: Incorrect Access Control - CWE-648. The impact is: Remote Code Execution. The component is: assets/components/fred/web/elfinder/connector.php. The attack vector is: Uploading a PHP file or change data in the database. The fixed version is: https://github.com/modxcms/fred/commit/139cefac83b2ead90da23187d92739dec79d3ccd and https://github.com/modxcms/fred/commit/01f0a3d1ae7f3970639c2a0db1887beba0065246.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Fred for MODX Revolution before 1.0.0-beta5 had an access-control flaw that could let an attacker reach remote code execution. For a business, the concern is compromise of affected MODX sites if the vulnerable Fred component is installed and reachable.

Executive priority

Treat as a high-priority legacy web exposure if Fred is installed. The business risk is site takeover through remote code execution, but urgency depends on whether affected versions are still deployed and reachable.

Technical view

CVE-2019-1010178 is CWE-648 in Fred MODX Revolution before 1.0.0-beta5. The named component is assets/components/fred/web/elfinder/connector.php. The CVE states impact as remote code execution through PHP file upload or database data changes. No CVSS score is provided.

Likely exposure

Exposure is most likely on MODX Revolution sites running Fred earlier than 1.0.0-beta5. The source bundle does not prove whether the vulnerable connector is publicly reachable by default or requires authentication.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. It only states the attack vector at a high level: uploading a PHP file or changing database data.

Researcher notes

Evidence is sparse: no CVSS vector, no detailed advisory, and no confirmed exploitation in the provided bundle. Focus validation on package version, connector exposure, and presence of the two upstream fixes.

Mitigation direction

  • Upgrade Fred to 1.0.0-beta5 or later if available.
  • Apply the two referenced upstream fixed commits if direct upgrade is unavailable.
  • Restrict access to the Fred elFinder connector until patch status is confirmed.
  • Review vendor or project guidance for any additional hardening steps.

Validation and detection

  • Inventory MODX Revolution sites using the Fred extra.
  • Confirm each Fred version is not earlier than 1.0.0-beta5.
  • Check whether assets/components/fred/web/elfinder/connector.php is reachable.
  • Review web and application logs for unexpected connector access or upload activity.
  • Verify the referenced fixed commits are present in deployed code.
Prepared
Confidence
medium
Sources
5

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.

cwe · low confidence lookup

CWE-648: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-1010178 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
FredMODX Revolution< 1.0.0-beta5 [fixed: https://github.com/modxcms/fred/commit/139cefac83b2ead90da23187d92739dec79d3ccd and https://github.com/modxcms/fred/commit/01f0a3d1ae7f3970639c2a0db1887beba0065246]Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-648 · source CWE mapping

Incorrect Use of Privileged APIs

Incorrect Use of Privileged APIs represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.