Skip to main content
Mallory
CriticalVulnerability

CVE-2023-29630: SQL Injection in PrestaShop jmsmegamenu (ajax_jmsmegamenu.php)

Published Jun 5, 2023 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS1.0%65th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Joommasters
IdentifiersCVE-2023-29630CWE-89 · Improper Neutralization of Special…

PrestaShop module jmsmegamenu versions 1.1.x and 2.0.x contain a SQL injection vulnerability in the ajax endpoint ajax_jmsmegamenu.php, where attacker-controlled input can be incorporated into SQL queries without adequate sanitization/parameterization, enabling injection of arbitrary SQL.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation may allow an attacker to execute arbitrary SQL queries against the underlying PrestaShop database, potentially resulting in unauthorized data access (e.g., customer/admin data), data modification, and in some cases authentication bypass or administrative compromise depending on what the vulnerable query touches and the database/account privileges used by the application.

Mitigation

If you can’t patch tonight, do this now.

Until a fixed module version is deployed, restrict access to ajax_jmsmegamenu.php (e.g., via WAF rules, IP allowlisting, or requiring authentication if feasible), monitor for suspicious requests containing SQL metacharacters/tautologies, and apply least-privilege to the database user used by PrestaShop to limit the blast radius of SQL injection.

Remediation

Patch, then assume compromise.

Upgrade the jmsmegamenu module to a fixed version provided by the vendor (information not available in the provided content). Ensure the vulnerable code path in ajax_jmsmegamenu.php uses parameterized queries (e.g., PrestaShop DbQuery with proper escaping/binding) and validates/normalizes all request parameters before use in SQL.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
JoommastersJms Drop Mega Menuapplication
FAQ

Frequently asked questions

Is CVE-2023-29630 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2023-29630?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2023-29630.
Is there a patch for CVE-2023-29630?
Upgrade the jmsmegamenu module to a fixed version provided by the vendor (information not available in the provided content). Ensure the vulnerable code path in ajax_jmsmegamenu.php uses parameterized queries (e.g., PrestaShop DbQuery with proper escaping/binding) and validates/normalizes all request parameters before use in SQL.
What products are affected by CVE-2023-29630?
Joommasters Jms Drop Mega Menu.
How severe is CVE-2023-29630?
CVE-2023-29630 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 1.0% (65th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.