HIGH 7.3

CVE-2026-12204: ShopXO Authorization Bypass in Order & Payment Processing

ShopXO, an e-commerce platform, contains a flaw that allows attackers to bypass authentication controls and manipulate critical order and payment functions without proper authorization. The vulnerability affects versions up to 6.7.1 and resides in the scheduled task endpoint responsible for order closure, payment logging, and reward processing. Because no authentication checks guard these functions, a remote attacker can invoke them directly to alter order states, process payments, or award bonuses without logging in. The vulnerability is publicly known and exploit code is available, increasing active risk.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.3 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Weaknesses (CWE)
CWE-285, CWE-639
Affected products
0 configuration(s)
Published / Modified
2026-06-15 / 2026-06-17

NVD description (verbatim)

A vulnerability was determined in ShopXO up to 6.7.1. This vulnerability affects the function OrderClose/OrderSuccess/PayLogOrderClose/GoodsGiveIntegral of the file app/api/controller/Crontab.php of the component Scheduled Task Endpoint. Executing a manipulation can lead to authorization bypass. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

5 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-12204 is an authorization bypass vulnerability in ShopXO's Crontab.php scheduled task controller. The affected functions—OrderClose, OrderSuccess, PayLogOrderClose, and GoodsGiveIntegral—perform sensitive operations (order finalization, payment reconciliation, and loyalty point allocation) but lack proper access control enforcement. The absence of authentication or session validation (CWE-285: Improper Authorization) combined with insufficient privilege separation (CWE-639: Authorization Bypass Through User-Controlled Key) enables unauthenticated remote code execution of these administrative functions. The CVSS 3.1 score of 7.3 (HIGH) reflects the network-accessible nature, low attack complexity, and partial impact to confidentiality, integrity, and availability.

Business impact

An attacker exploiting this vulnerability can alter order statuses without payment, initiate refunds or chargebacks, award fraudulent loyalty credits, or corrupt transaction records. For merchants using ShopXO, this translates to revenue loss (orders marked complete without payment), inventory mismanagement, customer account manipulation, and potential regulatory exposure for payment card handling violations. The publicly disclosed status means threat actors are actively testing and deploying attacks, making exploitation likely if systems remain unpatched.

Affected systems

ShopXO installations running version 6.7.1 and earlier are vulnerable. The attack vector is the Crontab.php endpoint, typically exposed via the application's API or scheduled task interface. Any organization operating an unpatched ShopXO deployment—whether on-premise or cloud-hosted—is immediately at risk. Verify your installed version against your deployment records.

Exploitability

Exploitability is high. The vulnerability requires no authentication, no special user interaction, and minimal complexity—an attacker simply calls the affected functions via HTTP request to the scheduled task endpoint. Public disclosure means proof-of-concept code is circulating, lowering the barrier for opportunistic attackers. No KEV listing is confirmed, but the public exploit availability and vendor non-response warrant immediate prioritization.

Remediation

Upgrade ShopXO to a patched version released after 6.7.1 that includes proper authorization checks on all scheduled task functions. If an upgrade is not immediately available, implement network-level access controls to restrict the Crontab.php endpoint to trusted internal or administrative IP ranges only, and monitor invocation logs for suspicious patterns. Verify with the vendor that the patched version fully validates authentication and session state before processing order or payment operations.

Patch guidance

Contact your ShopXO vendor or consult their official advisory for the specific patched version that addresses CVE-2026-12204. Apply the patch to all production and staging instances. After patching, verify that order closure, payment logging, and reward distribution functions now require proper authentication. Test the patch in a non-production environment first to ensure no regression in legitimate scheduled task execution.

Detection guidance

Monitor web server and application logs for HTTP requests to /app/api/controller/Crontab.php or related scheduled task endpoints that lack valid session tokens or authenticated user context. Flag any direct calls to OrderClose, OrderSuccess, PayLogOrderClose, or GoodsGiveIntegral functions from external IP addresses. Implement rate limiting on the Crontab endpoint to reduce the velocity of exploitation attempts. Review database logs for unexpected order status changes, payment transactions, or loyalty point allocations occurring outside normal business processes.

Why prioritize this

This vulnerability merits immediate remediation due to the combination of high CVSS score (7.3), public exploit availability, remote accessibility, and high business impact. The vulnerability directly endangers financial transactions and order integrity—core functions of an e-commerce platform. Vendor non-response increases uncertainty about patch timelines, making compensating controls and network segmentation critical interim measures.

Risk score, explained

The CVSS 3.1 score of 7.3 (HIGH) reflects an attack that can be launched remotely over a network (AV:N), requires no special user privileges or interaction (PR:N, UI:N), and causes partial disclosure, alteration, or disruption of system functionality (C:L, I:L, A:L). The score does not account for public exploit availability or vendor non-responsiveness, both of which increase practical risk. Organizations should treat this as a 'critical' business issue despite the technical HIGH rating.

Frequently asked questions

What versions of ShopXO are vulnerable?

ShopXO versions 6.7.1 and earlier are affected. If you are running 6.7.1 or below, assume your installation is vulnerable unless a specific patch has been applied. Verify your exact version in your ShopXO installation settings or package manifest.

Can I work around this vulnerability without upgrading?

A complete workaround without upgrading is not reliable. However, you can reduce immediate risk by restricting network access to the Crontab.php endpoint via firewall or web application firewall rules, limiting it to internal or whitelisted administrative IP ranges only. This is a temporary mitigation—patching should still be your primary goal.

How can I tell if my ShopXO instance has been exploited?

Review your order database for orders that transitioned to 'closed' or 'completed' status without corresponding payment records, or payment transactions that reference unusual or missing order IDs. Check application and web server logs for requests to Crontab.php endpoints from unexpected source IPs. Audit loyalty point balances for unexplained increases. If you detect suspicious activity, isolate the affected instance and engage your incident response team.

The vendor has not responded—should I switch platforms?

Vendor non-response is concerning and should influence your long-term platform strategy. In the short term, apply compensating controls (network segmentation, strict logging, frequent backups) and monitor for updates. Contact the vendor directly through their official channels to escalate. If no patch is released within a reasonable timeframe (e.g., 30 days), consider planning a migration to an actively maintained alternative.

This analysis is based on publicly disclosed information available as of the publication date. Vendor and version information should be verified against official advisories and your specific deployment. CVSS scores are technical severity ratings and do not account for organizational context, business criticality, or incident response readiness. Patch versions, release dates, and vendor response timelines may change; consult official vendor advisories for the most current remediation guidance. This intelligence is provided for authorized security professionals to support vulnerability management and risk prioritization within their organizations. Source: NVD (public-domain), retrieved 2026-07-20. Analysis generated by SEC.co (claude-haiku-4-5).