External risk intelligence

MaxSite CMS AJAX Dispatcher Authentication Bypass

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-70552

MaxSite CMS is a web application designed to be hosted on public web servers. As a CMS, the core functionality is intended for internet access, and the vulnerable AJAX dispatcher is part of the standard web-facing interface, making it commonly accessible to remote users via standard HTTP/HTTPS requests.

Missing Authentication

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in MaxSite CMS allows unauthenticated attackers to bypass security controls and access privileged administrative functions. This could enable unauthorized manipulation of sensitive data or system configurations within the content management system.

  • Attackers bypass login to access admin features.
  • Critical for systems using this content management.
  • Assess exposure to sensitive CMS functions.

Attack Path

How an attacker could exploit the issue

An attacker can initiate an attack by sending specially crafted requests to the web application. By manipulating HTTP headers and request paths, they can bypass normal authentication checks and gain access to administrative functions. This bypass targets the AJAX dispatcher, allowing access to privileged plugin endpoints that can then be used to manipulate poll data, modify vote counts, or execute other sensitive administrative actions.

  • Unauthenticated access to web interface.
  • Bypasses authentication via crafted requests.
  • Manipulates privileged plugin functions.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, unauthenticated attackers could access privileged endpoints within the MaxSite CMS. This vulnerability may allow manipulation of poll states and vote counts, and amplify the impact of other dangerous operations performed by admin-only AJAX files.

  • Poll states and vote counts at risk.
  • Unauthenticated AJAX dispatcher bypass.
  • Amplified impact of dangerous operations.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability likely impacts teams managing web applications and content management systems, including application owners and infrastructure teams. The immediate first step is to identify all instances of the affected CMS, confirm their exposure to the internet, and determine their business criticality. Once identified and prioritized, a remediation plan should be developed, potentially involving vendor coordination or temporary risk reduction measures.

  • Application owners, infrastructure teams.
  • Confirm internet exposure and criticality.
  • Plan remediation or vendor engagement.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is MaxSite CMS?

MaxSite CMS is a web-based content management system used to build and manage websites. It provides a framework for site owners to organize content, utilize plugins for added features like polls, and manage administrative settings through a browser-based interface.

What does CWE-306 mean for CVE-2026-70552?

CWE-306 is the weakness class for Missing Authentication for Critical Function. In this CVE, it means the application fails to verify who a user is before allowing them to trigger sensitive background tasks. Because of this, the software assumes a request is legitimate without checking for valid credentials, letting an unauthorized user interact with administrative code.

How does an attacker trigger this bypass?

An attacker triggers the vulnerability by sending a specific HTTP request to the AJAX dispatcher. They must include a particular header named X-Requested-With and provide a base64-encoded path that points to an admin-restricted file ending in *-ajax.php. Notably, simply browsing the site or sending standard requests without these specific modifications will not trigger the bug.

Is my site at risk according to Halo Surface Signal?

Yes, if your instance is internet-facing. Halo Surface Signal identifies this as a high-risk scenario because MaxSite CMS is designed for public web servers. Since the vulnerable AJAX dispatcher is part of the standard web-facing interface, remote users can reach it over the internet without needing access to your internal network.

How should I respond to this vulnerability?

Start by auditing your environment to locate all running instances of MaxSite CMS. Once identified, evaluate which sites are accessible from the internet and prioritize them for protection. Coordinate with your team to review the vendor's site for official updates and apply them as soon as possible to secure the dispatcher.

References