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

Back
New CVE Detected

CVE-2026-79322 – Unauthenticated SQL Injection – Mageplaza Blog for Magento 2 (through 4.3.2)

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-79322 is an unauthenticated SQL injection vulnerability in the Mageplaza Blog for Magento 2 extension (mageplaza/magento-2-blog-extension), affecting all versions through 4.3.2. The flaw resides in the RelatedProduct block, which builds a database query by concatenating a user-supplied request parameter directly into a SQL WHERE clause. It carries a CVSS v3.1 base score of 8.6 (High) and requires no authentication or user interaction, making internet-facing Magento storefronts running this extension directly exploitable.

Technical details

  • Root cause: Block/Post/RelatedProduct.php reads the id request parameter and appends it, unquoted and uncast, into a Zend_Db_Select where() clause (->where('product_post.post_id = ' . $postId)) instead of using parameter binding.
  • Trigger conditions: sending a crafted id value to the /mpblog/post/view endpoint; the targeted blog post must have at least one related product configured for the vulnerable code path to execute.
  • Attack vector: a simple unauthenticated HTTP GET request over the network, e.g. /mpblog/post/view?id=1 AND SLEEP(5), with time-based behavior confirming injection.
  • Impact: arbitrary SQL command execution against the Magento database, enabling extraction of customer records, order history, product data, and potentially administrative credentials, as well as database-driven denial of service.

Affected software

  • Mageplaza Blog for Magento 2 (mageplaza/magento-2-blog-extension) — all versions through 4.3.2

Severity

  • CVSS v3.1 Base Score: 8.6 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

Mitigation and recommended actions

  • Immediate: no official patched version has been published as of disclosure; monitor the vendor’s repository for a fixed release and upgrade as soon as one is available.
  • If no patch: restrict or filter requests to /mpblog/post/view at the WAF/reverse-proxy layer, validate that the id parameter is strictly numeric before it reaches the application, and monitor for anomalous or time-delayed requests to this endpoint. Consider disabling the RelatedProduct feature/module if not in use until a fix is released.

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