Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2023-30194: SQL Injection in PrestaShop posstaticfooter getPosCurrentHook()

Published May 10, 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
EPSS32.4%98th percentile
CISA KEVNoNot listed
In the wildReported3 exploitation records in Mallory
Vendor
Prestashop
IdentifiersCVE-2023-30194CWE-89 · Improper Neutralization of Special…

CVE-2023-30194 is a SQL injection vulnerability in the PrestaShop posstaticfooter module affecting versions up to and including 1.0.0. The issue is reported in the posstaticfooter::getPosCurrentHook() function, where attacker-controlled input is insufficiently sanitized or parameterized before being incorporated into SQL queries. This can allow crafted input to alter the structure of backend database queries.

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 can allow an attacker to manipulate application database queries. Depending on the query context, database permissions, and application behavior, this may enable unauthorized reading of data, modification or deletion of records, authentication bypass in some scenarios, or other database-level impacts. In some environments, SQL injection may also be leveraged for further compromise if the database and application configuration permit it.

Mitigation

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

If an immediate patch is not available, restrict access to the vulnerable functionality as much as possible, including limiting exposure to trusted users or networks where feasible. Deploy web application firewall rules or virtual patching to detect and block SQL injection payloads targeting the affected module and function. Enable detailed database and application logging to identify exploitation attempts, and ensure the database account used by the application has the minimum privileges necessary to reduce impact.

Remediation

Patch, then assume compromise.

Upgrade the PrestaShop posstaticfooter module to a fixed version if one is available from the vendor or maintainer. Review the implementation of getPosCurrentHook() and replace any dynamic SQL construction using untrusted input with parameterized queries or properly prepared statements. Apply strict server-side input validation and output encoding where appropriate, and audit similar code paths in the module for related injection flaws.

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
PrestashopPoststaticfooterapplication
FAQ

Frequently asked questions

Is CVE-2023-30194 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-30194?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2023-30194.
Is there a patch for CVE-2023-30194?
Upgrade the PrestaShop posstaticfooter module to a fixed version if one is available from the vendor or maintainer. Review the implementation of getPosCurrentHook() and replace any dynamic SQL construction using untrusted input with parameterized queries or properly prepared statements.
What products are affected by CVE-2023-30194?
Prestashop Poststaticfooter.
How severe is CVE-2023-30194?
CVE-2023-30194 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 32.4% (98th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

5 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 signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity4Community discussion across Reddit, Mastodon, and other social sources.