/

CVE-2026-12204

Severity:

HIGH RISK

(7.3)

Authorization Bypass (CWE-285) in ShopXO Cron API Tasks

CVE-2026-12204

Deferred

Vulnerability type

Category:

Authorization Bypass

CWE:

CWE-285, CWE-639

Impact:

Unauthorized Business Logic Execution

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

ShopXO up to version 6.7.1 contains an authorization bypass in several scheduled task endpoints within the Crontab controller.

A remote attacker can trigger order-closing and related actions without proper permission checks, potentially manipulating order state and user benefits when these endpoints are exposed.

Affected context

The vulnerability occurs in ShopXO deployments that expose the app/api/controller/Crontab.php scheduled task endpoints (OrderClose, OrderSuccess, PayLogOrderClose, GoodsGiveIntegral) over HTTP.

It is most relevant when these cron-like routes are reachable from untrusted networks and rely on weak, missing, or purely client-controlled authorization controls.

In such setups, background job actions that should be limited to trusted automation can be invoked directly by arbitrary remote clients, leading to changes in order lifecycle and reward handling.

Exploit preconditions

  • Attack surface: Public or semi-public HTTP endpoints mapped to Crontab.php actions.
  • Required access: Network access to the ShopXO API; no valid user session or elevated role is strictly required if the authorization checks are weak or missing.
  • Trigger point: Direct invocation of scheduled task endpoints such as OrderClose, OrderSuccess, PayLogOrderClose, or GoodsGiveIntegral.
  • Why exploitation is possible: The affected actions perform sensitive business operations while relying on inadequate authorization enforcement (CWE-285) and potentially insecure user or resource ID references (CWE-639), allowing callers to influence order state and user-related operations beyond their privileges.

Why this happens

The issue stems from insufficient enforcement of authorization on sensitive cron-style endpoints within the Crontab controller.

Functions like OrderClose, OrderSuccess, PayLogOrderClose, and GoodsGiveIntegral encapsulate privileged business logic—closing orders, marking them successful, finalizing payment logs, and granting points—but do not consistently verify that the caller is a trusted scheduler or properly authenticated and authorized principal.

This aligns with CWE-285: Improper Authorization, where access control decisions are missing or incomplete, and CWE-639: Authorization Bypass Through User-Controlled Key, when identifiers or parameters referencing orders or users can be manipulated by clients to affect resources they do not own.

In abstract terms, business logic intended for internal automation is exposed as a general HTTP API without robust access control boundaries.

Potential impact

  • Attackers may close or mark orders as successful without legitimate payment completion.
  • Order state and payment logs can be manipulated, leading to reconciliation issues and financial loss.
  • Users may receive or be denied reward points or integrals inconsistently with real transactions.
  • Reporting, analytics, and downstream systems may be poisoned with falsified transactional data.
  • Automated fraud or abuse scenarios can be enabled by scripting repeated unauthorized actions.

General mitigation guidance

Mitigation generally focuses on enforcing strict access control on automated task endpoints and hardening business logic boundaries.

Recommended defensive patterns include:

  • Segregating internal cron or job endpoints from public API routes, limiting access to trusted networks or service accounts.
  • Implementing server-side authorization checks that verify both authentication and role/permission before executing order or reward operations.
  • Treating identifiers for orders and users as sensitive, validating that the acting principal is permitted to operate on the referenced resource.
  • Encapsulating critical state transitions (e.g., order close, success, payment finalization) behind centralized authorization and consistency checks.
  • Minimizing privileges for any automation tokens or scheduler credentials and rotating them regularly.

These measures make it harder for untrusted callers to leverage scheduled task logic for unauthorized business actions.

How teams detect issues like this

Detection efforts typically combine code-level analysis with runtime monitoring:

  • Static analysis and review: Scan controllers and background task handlers for endpoints that perform sensitive state changes without explicit authorization checks or middleware; flag uses of order/user identifiers that lack ownership validation.
  • Security code review: Examine Crontab.php and similar controllers for assumptions that certain routes are "internal only"; verify that access control enforcement is explicit and not merely implied by routing conventions.
  • Logging and monitoring: Enable detailed logging for calls to order-closing, payment-log, and reward-granting functions, including caller identity, source IP, and parameters, then alert on anomalous patterns (e.g., high volume from a single IP, actions outside expected scheduler times).
  • Policy enforcement in CI/CD: Use automated review tools or custom rules to block deployment when new endpoints with high-impact business logic are introduced without accompanying authorization checks.

Over time, these strategies can help organizations identify similar authorization gaps before they reach production or are exploited.

Sources

SourceLink
github.comgithub.com/yunyan05/MYCVE/tree/main/ShopXO/V6.7.1-Unauthenticated-Crontab-Trigger
vuldb.comvuldb.com/cve/CVE-2026-12204
vuldb.comvuldb.com/submit/830800
vuldb.comvuldb.com/vuln/370847
vuldb.comvuldb.com/vuln/370847/cti

Frequently asked

questions

Yes, if the ShopXO scheduled task endpoints are reachable from the internet or any untrusted network, a remote attacker can attempt to invoke them directly. If they are constrained to an internal network segment, exposure is limited to actors with access to that environment.

In many misconfigurations it may not. The core issue is missing or inadequate authorization checks on the affected endpoints, so exploitation could be possible with only network access. However, some deployments might still require some form of authentication, which can reduce but not eliminate risk if authorization remains weak.

The safest pattern is to treat cron and automation endpoints as privileged operations: enforce strong server-side authorization, restrict access to trusted schedulers or networks, and centralize business logic checks so that state-changing actions are never performed without validating both the caller and the target resource.

Organizations can adopt consistent access control frameworks, require explicit authorization for every endpoint that changes business state, and mandate security review for controllers handling orders, payments, or rewards. Adding automated tests and static checks for missing authorization, and separating internal automation APIs from public-facing routes, also reduces the likelihood of similar bugs.

Find out what's already
exploitable in your codebase.