SQL injection vulnerability in Webbax supernewsletter v.1.4.21 and before allows a remote attacker to escalate privileges via the Super Newsletter module in the product_search.php components.
Vendor
Webbax vulnerabilities
8 published CVES affecting Webbax, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 8
- Critical
- 2
- High
- 5
- Medium
- 1
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Products
- supernewsletter 2
- customexporter 1
- King-Avis 1
- myinventory 1
- postfinance 1
- salesbooster 1
- super newsletter 1
- winbizpayment 1
Latest Webbax CVEs
Newest publication first
-
CriticalCVSS 9.8 EPSS 0.68%
-
HighCVSS 7.5 EPSS 0.45%
An issue was discovered in Webbax "Super Newsletter" (supernewsletter) module for PrestaShop versions 1.4.21 and before, allows local attackers to escalate privileges and obtain sensitive information.
-
CriticalCVSS 9.8 EPSS 0.62%
PrestaShop postfinance <= 17.1.13 is vulnerable to SQL Injection via PostfinanceValidationModuleFrontController::postProcess().
-
HighCVSS 7.5 EPSS 5.5%
Prestashop winbizpayment <= 1.0.2 is vulnerable to Incorrect Access Control via modules/winbizpayment/downloads/download.php.
-
MediumCVSS 4.9 EPSS 0.79%
Improper Limitation of a Pathname leads to a Path Traversal vulnerability in the module King-Avis for Prestashop, allowing a user knowing the download token to read arbitrary local files.This issue affects King-Avis: before 17.3.15.
-
HighCVSS 7.5 EPSS 0.70%
Incorrect Access Control in the module "My inventory" (myinventory) <= 1.6.6 from Webbax for PrestaShop, allows a guest to download personal information without restriction by performing a path traversal attack.
-
HighCVSS 7.5 EPSS 0.50%
Prestashop salesbooster <= 1.10.4 is vulnerable to Incorrect Access Control via modules/salesbooster/downloads/download.php.
-
HighCVSS 7.5 EPSS 0.70%
Prestashop customexporter <= 1.7.20 is vulnerable to Incorrect Access Control via modules/customexporter/downloads/download.php.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.