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

Back
New CVE Detected

CVE-2026-81567 – Unauthenticated Blind SQL Injection – J2Store Joomla Extension 1.0.0–3.3.22, 4.0.0–

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-81567 is an unauthenticated blind SQL injection vulnerability in J2Store, a Joomla e-commerce extension published by j2commerce.com. The flaw resides in the storefront product listing functionality and allows a remote, unauthenticated attacker to extract arbitrary database content through boolean- or time-based inference. The issue carries a HIGH severity rating (CVSS 8.7) because it requires no authentication or user interaction and is reachable on any public storefront.

Technical details

  • Root cause: Improper neutralization of user-supplied input used to construct SQL queries (CWE-89) in the code that renders the storefront product list and product-tags filter.
  • Trigger conditions: The vulnerable code path is reachable on any public-facing J2Store storefront that exposes the standard product listing or product-tags filtering feature — no login or special configuration is required.
  • Attack vector: Network-based; an attacker sends crafted input to the product list/filter parameters and observes boolean (true/false) or time-based (response delay) differences to infer database contents.
  • Impact: Blind, unauthenticated extraction of arbitrary database content, including customer records, order data, and potentially stored credentials or tokens. There is no direct impact to integrity or availability — the confidentiality impact is the primary concern.

Affected software

  • J2Store extension for Joomla, versions 1.0.0 through 3.3.22
  • J2Store extension for Joomla, versions 4.0.0 through 4.0.22
  • J2Store extension for Joomla, versions 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:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade J2Store to a release beyond the affected ranges — i.e., beyond 3.3.22 on the 3.x branch, beyond 4.0.22 on the 4.0.x branch, or beyond 4.1.7 on the 4.1.x branch. Consult the vendor (j2commerce.com) for the specific patched build applicable to your branch.
  • If immediate patching is not possible: Restrict or disable public access to the storefront product listing and product-tags filtering features where feasible, deploy a web application firewall rule to block boolean/time-based SQL injection patterns on storefront parameters, and monitor database and web server logs for anomalous, delayed, or repetitive query patterns indicative of blind SQL injection probing.
  • Rotate any credentials or tokens that may be stored in the affected database tables as a precaution following patching.

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