Skip to main content
Vulnerability Database/CVE-2026-114391

CVE-2026-114391: ZenTao PMS Authorization Bypass Vulnerability

CVE-2026-114391 is an authorization bypass flaw in ZenTao PMS that allows logged-in users to skip ACL checks and access sensitive methods. Attackers can read data, obtain credentials, and alter databases. This article covers technical details, affected versions, impact assessment, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-114391 Overview

CVE-2026-114391 is an authorization bypass vulnerability in ZenTao PMS versions before 22.3. The flaw resides in the commonModel::isOpenMethod() function, which incorrectly whitelists any controller method whose name contains the substring ajax. Authenticated users with minimal privileges can invoke sensitive methods such as task.ajaxGetByID, system.ajaxDBAuthUrl, and admin.ajaxChangeTableEngine. These calls allow attackers to read restricted project data, exfiltrate database credentials, trigger continuous integration jobs, and alter database table engines without passing group-based ACL checks. The issue is tracked as CWE-863: Incorrect Authorization.

Critical Impact

Any authenticated low-privilege ZenTao PMS user can bypass access control, read sensitive project data, obtain database credentials, and modify database structures through ajax-named controller methods.

Affected Products

  • ZenTao PMS versions prior to 22.3
  • module/common/model.php — isOpenMethod() function
  • module/system/control.php ajax endpoints including ajaxDBAuthUrl

Discovery Timeline

  • 2026-10-21 - CVE-2026-114391 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-114391

Vulnerability Analysis

ZenTao PMS enforces access control through group-based ACLs applied in commonModel::isOpenMethod(). Before version 22.3, that function returned true for any logged-in user whenever the requested method name contained the string ajax. The check used a case-insensitive substring match via stripos($method, 'ajax') !== false.

This blanket exemption was intended to simplify asynchronous UI calls. In practice it bypassed the entire ACL layer for a large set of sensitive controller actions. Attackers do not need an administrator session. A standard authenticated account, or even the guest account when guest access is enabled, is sufficient to reach these endpoints.

The exposed methods include task.ajaxGetByID for arbitrary task data retrieval, system.ajaxDBAuthUrl for database credential disclosure, and admin.ajaxChangeTableEngine for schema modification. Credential disclosure enables lateral movement to the backing MySQL instance.

Root Cause

The root cause is overly permissive pattern matching in authorization logic. isOpenMethod() treated the naming convention ajax as a security boundary rather than a UI hint. No cross-check validated whether the caller actually had privilege to invoke the underlying action.

Attack Vector

An attacker authenticates with any valid account and issues an HTTP request to a controller endpoint whose method name contains ajax. The ACL check short-circuits and returns the method output directly. The attack is remote, requires low privileges, and needs no user interaction.

php
// Vulnerable logic removed in the patch (module/common/model.php)
if($this->loadModel('user')->isLogon() or ($this->app->company->guest and $this->app->user->account == 'guest'))
{
    if(in_array("$module.$method", $this->config->logonMethods)) return true;

    // Removed: blanket allow for any method name containing 'ajax'
    if(stripos($method, 'ajax') !== false) return true;
    // ...
}

Source: ZenTao commit ac484f3

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-114391

Indicators of Compromise

  • HTTP requests from low-privilege sessions to URLs invoking system.ajaxDBAuthUrl, admin.ajaxChangeTableEngine, or other *.ajax* methods outside normal UI flows.
  • Unexpected calls to task.ajaxGetByID enumerating sequential task identifiers from a single session.
  • Web server access logs showing ajax endpoints invoked without the referring ZenTao UI page.
  • Database audit entries showing ALTER TABLE ... ENGINE= statements originating from the ZenTao application user outside maintenance windows.

Detection Strategies

  • Baseline normal usage of ajax controller methods per user role and alert on invocations by accounts that never previously accessed them.
  • Inspect web application firewall logs for direct requests to m=system&f=ajaxDBAuthUrl or m=admin&f=ajaxChangeTableEngine style URLs.
  • Correlate authenticated low-privilege sessions with sensitive ajax endpoint access across the Singularity Data Lake using OCSF-normalized web and application telemetry.

Monitoring Recommendations

  • Enable verbose logging on the ZenTao PHP application tier to capture module and method parameters per request.
  • Monitor the MySQL account used by ZenTao for schema change statements and privilege-sensitive reads.
  • Alert on repeated 200-status responses to ajax endpoints that return credential or configuration data.

How to Mitigate CVE-2026-114391

Immediate Actions Required

  • Upgrade ZenTao PMS to version 22.3 or later, which replaces the blanket ajax exemption with explicit per-method dependency checks.
  • Audit user accounts and remove unused low-privilege accounts that could be leveraged for the bypass.
  • Rotate the database credentials returned by system.ajaxDBAuthUrl if the pre-patch version was exposed to untrusted users.

Patch Information

The fix is included in ZenTao PMS release 22.3 and introduced in commit ac484f3b01c0f84002391a344d99dd2993692f49. The patch adds a privilege.php configuration and an ajaxDependencies map. Ajax methods are only permitted when the caller also has privilege for the declared dependent method.

php
// Patched logic (module/common/model.php)
if(stripos($method, 'ajax') !== false && !empty($this->config->ajaxDependencies["$module.$method"]))
{
    $dependentMethods = $this->config->ajaxDependencies["$module.$method"];
    if(is_string($dependentMethods)) $dependentMethods = [$dependentMethods];
    if(is_array($dependentMethods))
    {
        foreach($dependentMethods as $dependentMethod)
        {
            if(strpos($dependentMethod, '.') === false) continue;
            list($dependentModule, $dependentMethod) = explode('.', $dependentMethod);
            if($this->isOpenMethod($dependentModule, $dependentMethod) || self::hasPriv($dependentModule, $dependentMethod)) return true;
        }
    }
}

Source: ZenTao commit ac484f3. Additional detail is available in the VulnCheck advisory and GitHub issue #181.

Workarounds

  • Restrict network access to the ZenTao PMS interface to trusted internal networks or VPN users until the upgrade is applied.
  • Disable guest access by setting $this->app->company->guest to false to prevent unauthenticated reach to ajax endpoints.
  • Deploy WAF rules that block external requests targeting system.ajaxDBAuthUrl, admin.ajaxChangeTableEngine, and other sensitive ajax methods identified in the advisory.
bash
# Example WAF rule (ModSecurity) blocking high-risk ajax endpoints
SecRule REQUEST_URI "@rx (?i)(m=system&f=ajaxDBAuthUrl|m=admin&f=ajaxChangeTableEngine)" \
    "id:1026114391,phase:1,deny,status:403,log,msg:'CVE-2026-114391 ZenTao ajax ACL bypass attempt'"

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.