Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-78064 – Authorization Bypass / Cart Tampering – J2Store Joomla Extension 1.0.0–3.3.21, 4.0.

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-78064 is an authorization bypass vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) in the J2Store e-commerce extension for Joomla. It allows an unauthenticated attacker to insert or overwrite shopping cart records belonging to other users. The flaw carries a severity score of 8.8 (HIGH).

Technical details

  • Root cause: J2Store’s fof.xml grants wildcard ACL permissions to the "carts" view’s tasks, and the underlying FOF framework only enforces CSRF token checks on back-end HTML requests, not on front-end format=raw requests.
  • J2StoreControllerCarts overrides and restricts the remove() function to the calling session, but never overrides the generic, inherited FOF save task.
  • This leaves the save task reachable by anonymous front-end requests, allowing an attacker to submit a request with an attacker-controlled user_id/session_id to insert a new cart row or overwrite an existing cart record by its ID.
  • Attack vector: network, no privileges and no user interaction required.
  • Impact: unauthenticated tampering with other users’ cart data (integrity impact), potentially enabling manipulation of orders/checkout data tied to another user’s session.

Affected software

  • J2Store (Joomla extension, j2commerce.com) versions 1.0.0 through 3.3.21
  • J2Store versions 4.0.0 through 4.0.21
  • J2Store versions 4.1.0 through 4.1.6

Severity

  • Base score: 8.8 (HIGH)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
  • Attack vector: Network, Privileges Required: None, User Interaction: None

Mitigation and recommended actions

  • Immediate: No specific patched version number was published in the disclosure at the time of writing. Site owners should check the J2Store vendor site (j2commerce.com) and update to the latest available release, and monitor for a vendor advisory confirming a fixed build.
  • If no patch is available: restrict or monitor front-end format=raw requests to the carts controller; deploy WAF/reverse-proxy rules to block anonymous requests invoking the save task on cart endpoints; review J2Store ACL configuration in fof.xml for overly permissive wildcard rules; monitor cart/order data for unexpected user_id/session_id values.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: /media/j2store/, /components/com_j2store/

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