8.8
CVE-2022-3494
- EPSS 0.92%
- Veröffentlicht 07.11.2022 10:15:12
- Zuletzt bearbeitet 01.05.2025 20:15:33
- Quelle contact@wpscan.com
- CVE-Watchlists
- Unerledigt
Complianz Free <= 6.3.3 & Premium <= 6.3.5 - SQL Injection via Translations
The Complianz WordPress plugin before 6.3.4, and Complianz Premium WordPress plugin before 6.3.6 allow a translators to inject arbitrary SQL through an unsanitized translation. SQL can be injected through an infected translation file, or by a user with a translator role through translation plugins such as Loco Translate or WPML.
Mögliche Gegenmaßnahme
Complianz – GDPR/CCPA Cookie Consent: Update to version 6.3.4, or a newer patched version
Complianz Premium – GDPR/CCPA Cookie Consent: Update to version 6.3.6, or a newer patched version
Weitere Schwachstelleninformationen
SystemWordPress Plugin
≫
Produkt
Complianz – GDPR/CCPA Cookie Consent
Version
*-6.3.3
SystemWordPress Plugin
≫
Produkt
Complianz Premium – GDPR/CCPA Cookie Consent
Version
*-6.3.5
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Really-simple-plugins ≫ Complianz SwEdition- SwPlatformwordpress Version < 6.3.4
Really-simple-plugins ≫ Complianz SwEditionpremium SwPlatformwordpress Version < 6.3.6
| Typ | Quelle | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.92% | 0.752 |
| Quelle | Base Score | Exploit Score | Impact Score | Vector String |
|---|---|---|---|---|
| nvd@nist.gov | 8.8 | 2.8 | 5.9 |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
|
| 134c704f-9b21-4f2e-91b3-4a467353bcc0 | 8.8 | 2.8 | 5.9 |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
|
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.