Security readout for executives and security teams
Plain-English summary
This vulnerability affects the PrestaShop totadministrativemandate module before v1.7.1. A logged-in attacker could abuse SQL injection to read or alter sensitive store database data. The public record rates it high severity. The provided sources do not show known active exploitation.
Executive priority
Treat this as a high-priority patching item for any PrestaShop store using the affected module. Business risk centers on database confidentiality and integrity, including customer, order, or mandate-related data if stored in the affected database.
Technical view
CVE-2022-46965 is CWE-89 SQL injection in the PrestaShop totadministrativemandate module before v1.7.1. CVSS 3.1 is 8.1 with network access, low complexity, low privileges, no user interaction, high confidentiality and integrity impact, and no availability impact.
Likely exposure
Exposure is likely limited to PrestaShop deployments that have the totadministrativemandate module installed below v1.7.1. The source bundle does not provide CPEs or broader affected product metadata.
Exploitation context
The CVSS vector indicates remote network reachability and low attack complexity, but requires some level of privileges. The bundle marks KEV as false and provides no cited evidence of active exploitation.
Researcher notes
The public metadata is sparse: affected vendor/product fields and CPEs are listed as n/a. Analysis should therefore start with module inventory and vendor advisory review. Do not assume impact beyond PrestaShop totadministrativemandate before v1.7.1.
Mitigation direction
Inventory PrestaShop sites for the totadministrativemandate module.
Upgrade the module to v1.7.1 or later where installed.
If immediate upgrade is not possible, follow vendor advisory guidance.
Restrict module access to necessary authenticated users.
Review database and application logs for suspicious module activity.
Validation and detection
Confirm whether totadministrativemandate is installed on each PrestaShop instance.
Record the installed module version and flag anything below v1.7.1.
Check whether exposed environments require authentication for relevant module functions.
Review logs for SQL errors or unusual authenticated requests.
Verify the CVE is not listed as KEV in the provided bundle.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.