Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify MaxSite CMS ≤109.5 target
-
DeliveryCraft request with arbitrary X-Requested-With header
-
ExploitSupply base64 path to admin *-ajax.php
-
ExecutionDispatcher loads handler without auth check
-
PersistInvoke privileged poll/plugin operation
-
ImpactManipulate poll state and vote counts
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires only that the MaxSite CMS AJAX dispatcher be network-reachable (the default for a running site) and that the target run version 109.5 or earlier. The attacker must (1) supply any value for the X-Requested-With request header, which the dispatcher trusts as proof of a legitimate AJAX call, and (2) supply a base64-encoded path that resolves to a file matching the *-ajax.php naming pattern in the codebase. No credentials, session, or user interaction are needed (PR:N/UI:N). The practical limiting factor is impact scope rather than access: the severity of what an attacker can do depends on which admin-only *-ajax.php handlers exist in the specific installation and plugin set - the confirmed effect is poll/vote manipulation, while broader confidentiality or availability impact is contingent on the dangerous operations exposed by other admin AJAX files present. |
| Impact | The vendor CVSS 4.0 score of 9.3 (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H) reflects a network-reachable, low-complexity, unauthenticated flaw with high impact - consistent with the description, which requires only a crafted HTTP request against a default-reachable endpoint. There is no EPSS score, no SSVC decision, and no KEV listing in the provided data, so real-world exploitation cannot be confirmed and appears to be neither active nor mass-scanned at this time. The high VC/VI/VA rating is somewhat optimistic relative to the concretely demonstrated impact: the description proves integrity abuse (poll and vote manipulation) and states that the bypass 'amplifies the impact of any dangerous operation' in admin AJAX files, meaning full confidentiality/availability impact depends on what specific *-ajax.php handlers exist in a given deployment rather than being universally guaranteed. Net assessment: a genuine, easy-to-exploit unauthenticated access-control break that warrants prompt patching, tempered by the fact that MaxSite CMS is a niche product and no exploitation or POC has been observed in the provided intelligence. |
| Exploit ScenarioDerived | An unauthenticated attacker sends an HTTP request to the MaxSite CMS AJAX dispatcher, adding an arbitrary X-Requested-With header and a base64-encoded path pointing to a privileged handler such as a poll plugin's admin *-ajax.php file. The dispatcher loads and executes the admin handler without any credential check, letting the attacker alter poll states and inflate or reset vote counts, and reach any other admin-only AJAX operation present in the plugin tree. No POC is provided in the source data, but the low attack complexity and lack of authentication make reliable exploitation straightforward. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 04, 2026
Authentication bypass in MaxSite CMS version 109.5 and earlier lets unauthenticated remote attackers reach admin-gated AJAX endpoints by sending any X-Requested-With header alongside a base64-encoded path that resolves to any *-ajax.php file in the codebase. Because the dispatcher never verifies an admin session, attackers can invoke privileged plugin operations - demonstrated by manipulating poll states and vote counts - and can amplify any dangerous action exposed by admin-only AJAX files across the plugin tree. No public exploit identified at time of analysis, but the flaw was reported by VulnCheck and a fixed release (109.6) is available.
RemediationAI
Upgrade to MaxSite CMS 109.6, which contains the vendor fix (Vendor-released patch: 109.6); see the release notes at https://max-3000.com/page/maxsite-cms-109-6 and the VulnCheck advisory at https://www.vulncheck.com/advisories/maxsite-cms-unauthenticated-ajax-dispatcher-bypass-via-ajax-php. If immediate patching is not possible, restrict network access to the CMS administration and AJAX endpoints (for example, IP-allowlist or place the admin surface behind a VPN/reverse proxy) so unauthenticated internet clients cannot reach the dispatcher; the trade-off is that legitimate remote admins must connect through the allowed path. As a stopgap, a WAF rule can block or challenge requests to *-ajax.php that carry base64-encoded path parameters or an X-Requested-With header from unauthenticated sessions, but tune carefully because MaxSite's own front-end legitimately sends X-Requested-With, so an overly broad rule may break site AJAX functionality. Do not rely on header inspection alone as a permanent control - the underlying flaw is that the header is trusted as authentication.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
MaxSite CMS is a PHP-based content management system that routes asynchronous requests through a central AJAX dispatcher. The dispatcher gates access on the presence of an X-Requested-With header (the conventional marker of an XMLHttpRequest) and then loads a handler file whose path is supplied by the client as a base64-encoded value. The root cause is CWE-306 (Missing Authentication for a Critical Function): the dispatcher treats the mere presence of the X-Requested-With header as sufficient proof of a legitimate, authenticated admin context, when in fact any client can set that header to an arbitrary value. Combined with attacker-controlled path selection, this allows loading of any file matching the *-ajax.php naming convention - including handlers intended to run only for authenticated administrators. The affected CPE is cpe:2.3:a:maxsite:maxsite_cms:*:*:*:*:*:*:*:* across all versions up to and including 109.5.
Know when Maxsite Cms gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Unauthenticated network access with trivial complexity (AV:N/AC:L/PR:N/UI:N); confirmed impact is integrity (poll/vote manipulation, I:H) while C and A are only conditionally reachable via other admin handlers, so C:L/A:L.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
MaxSite CMS 109.5 and earlier contains an authentication bypass vulnerability in the AJAX dispatcher that allows unauthenticated attackers to access admin-gated endpoints by supplying any X-Requested-With header and requesting a base64-encoded path resolving to any *-ajax.php file in the codebase. Attackers can exploit this dispatcher bypass to reach privileged plugin endpoints without credentials, enabling actions such as manipulating poll states and vote counts, and amplifying the impact of any dangerous operation performed by admin-only ajax files across the plugin tree.
Articles & Coverage 1
Executive ViewAI
MaxSite CMS versions 109.5 and earlier contain a critical authentication bypass allowing unauthenticated attackers to execute administrative operations, including content and vote manipulation, without valid credentials. Organizations running affected versions face immediate risk to data integrity and compliance, requiring urgent upgrade to address this capability-level threat.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Maxsite Cms
View allA Remote Code Execution (RCE) vulnerability at /admin/options in Maxsite CMS v180 allows attackers to execute arbitrary
Remote Code Execution (RCE) vulnerability exists in MaxSite CMS v107.5 via the Documents page. Rated critical severity (
Authentication bypass in MaxSite CMS versions 0.78 through 109.6 lets unauthenticated remote attackers forge valid admin
PHP object injection in MaxSite CMS through version 109.6 lets unauthenticated remote attackers forge valid ci_session c
Local file inclusion in MaxSite CMS through 109.6 allows unauthenticated remote attackers to execute privileged PHP hand
Maxsite CMS v180 was discovered to contain multiple arbitrary file deletion vulnerabilities in /admin_page/all-files-upd
A reflected cross-site scripting (XSS) vulnerability in MaxSite CMS before V106 via product/page/* allows remote attacke
Maxsite Cms versions up to 109.1. contains a vulnerability that allows attackers to code injection (CVSS 7.3).
Persistent unauthenticated remote code execution in MaxSite CMS lets attackers POST a crafted db_dbprefix value to the i
Unauthenticated remote code execution in MaxSite CMS is possible because the application passes attacker-controlled seri
Maxsite CMS v108 was discovered to contain a stored cross-site scripting (XSS) vulnerability via the parameter f_tags at
Maxsite CMS v180 was discovered to contain a stored cross-site scripting (XSS) vulnerability via the parameter f_file_de
EUVD-2026-52909
GHSA-r998-r395-678g
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB