Security readout for executives and security teams
Plain-English summary
MaxSite CMS installations may allow anyone on the internet to place malicious PHP into a configuration file through the installation endpoint. The injected code then runs on later requests with web-server privileges, enabling persistent server compromise without authentication or user interaction.
Executive priority
Treat internet-facing instances as an immediate remediation priority because exploitation requires no account or user action and can produce persistent server-side code execution. Confirm exposure, restrict the installation endpoint, and obtain authoritative vendor correction guidance promptly.
Technical view
Crafted POST data can inject PHP through the db_dbprefix field by escaping a string literal written to application/config/database.php. Subsequent web requests execute the appended code. The supplied record rates this CVSS 9.8 and identifies CWE-94, with MaxSite CMS 105.2 and 109.6 listed as affected.
Likely exposure
Internet-facing MaxSite CMS 105.2 or 109.6 systems are potentially exposed when the installation endpoint remains reachable and can rewrite application/config/database.php after installation. The bundle does not establish whether every deployment exposes this endpoint by default or requires specific filesystem permissions.
Exploitation context
The attack is remotely reachable, low complexity, unauthenticated, and requires no user interaction. Successful exploitation could affect confidentiality, integrity, and availability. The supplied record is not in KEV, and the provided sources do not establish active exploitation in the wild.
Researcher notes
The bundle lists versions 105.2 and 109.6 as affected, while a reference labeled “Patch Commit” points to a 109.6 page. This ambiguity prevents identifying a safe fixed version from the supplied evidence. Validation should focus on endpoint reachability, configuration-file integrity, and web-server write access.
Mitigation direction
- Consult MaxSite guidance and apply a confirmed corrected release; the bundle does not identify an unambiguous fixed version.
- Until corrected, prevent untrusted access to the installation endpoint using server or network controls.
- Restrict web-server write permissions for configuration files where operationally feasible.
- If compromise is suspected, isolate the host and restore configuration and application files from trusted sources.
- Rotate database credentials and other secrets accessible to the web-server process after suspected compromise.
Validation and detection
- Inventory MaxSite CMS deployments and verify installed versions.
- Determine whether the installation endpoint remains publicly reachable after deployment.
- Check application/config/database.php for unexpected PHP statements or recent unauthorized changes.
- Review HTTP logs for anomalous POST requests targeting the installation endpoint.
- Assess related files, processes, and credentials if configuration tampering is found.
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.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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 lookupExecution 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 lookupDatabase 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 lookupCVE-2026-70553 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Product RepositoryCVE reference, VulnCheck · product
- Patch CommitCVE reference, VulnCheck · patch
- https://www.vulncheck.com/advisories/maxsite-cms-unauthenticated-rce-via-install-endpointCVE reference, VulnCheck · third-party-advisory
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.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.