PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

Back
New CVE Detected

CVE-2026-82189 – Unauthenticated Order Status Manipulation (DoS) – J2Store Joomla Extension 1.0.0–3.

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-82189 is a High-severity vulnerability in the J2Store e-commerce extension for Joomla that allows an unauthenticated attacker to mark any store order as "Failed" without any credentials or interaction from the order owner. Because the affected code fails to enforce server-side authorization over order-state transitions, an attacker can mass-fail pending orders or flip already-fulfilled orders back to a failed state, disrupting checkout pipelines and forcing manual reprocessing.

Technical details

  • Root cause: The order-status update path relies on a web parameter that is treated as trusted/immutable but is actually attacker-controlled (CWE-472: External Control of Assumed-Immutable Web Parameter), combined with security logic that is enforced on the client rather than validated server-side (CWE-602: Client-Side Enforcement of Server-Side Security).
  • Trigger conditions: No authentication, prior session, or special privileges are required; the request can be sent directly at the affected order-management endpoint.
  • Attack vector: Network-based (AV:N), low attack complexity, no privileges required, no user interaction.
  • Impact: High integrity impact on order records — attackers can revert paid/fulfilled orders to "Failed" or mass-fail pending orders, disrupting revenue recognition, fulfillment workflows, and creating operational confusion for the merchant. No confidentiality or availability impact to the underlying system was reported.

Affected software

  • J2Store (j2commerce.com) for Joomla, versions:
    • 1.0.0 through 3.3.22
    • 4.0.0 through 4.0.22
    • 4.1.0 through 4.1.7

Severity

  • CVSS v4.0 Base Score: 8.7 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade J2Store to a release beyond the affected version ranges (1.0.0–3.3.22, 4.0.0–4.0.22, 4.1.0–4.1.7) as soon as the vendor publishes a fixed build for the applicable branch, and confirm the update addresses server-side authorization on order-status transitions.
  • If no patch is yet available for your branch: Restrict or monitor access to order-management/order-status endpoints (e.g., via web application firewall rules or reverse-proxy access controls), and audit recent order history for unexpected transitions to "Failed" status that do not correspond to genuine payment or fulfillment events.
  • Review J2Store vendor advisories and the Joomla Security Announcements page regularly for the official patched version numbers for this issue.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge