Security readout for executives and security teams
Plain-English summary
This affects WordPress sites using the Paytm Payment Gateway plugin up to version 2.7.3. The reported flaw is SQL injection, which can let an attacker interfere with the site database. For a payment-related plugin, database confidentiality and integrity risk should be treated as urgent.
Executive priority
Treat as urgent for any WordPress site taking payments through this plugin. The risk is high because SQL injection can affect customer, order, and operational data, but urgency should be scoped to confirmed installations rather than assumed enterprise-wide exposure.
Technical view
CVE-2022-45805 is a CWE-89 SQL injection issue in the Paytm Payment Gateway WordPress plugin package paytm-payments through 2.7.3. The CVSS 3.1 score is 9.8 with network attack vector, low complexity, no privileges, and no user interaction in the supplied CVE metadata.
Likely exposure
Exposure is likely limited to WordPress installations with the Paytm Payment Gateway plugin installed and active at version 2.7.3 or earlier. Public-facing commerce sites are the highest concern because the component is payment-related and reachable from the internet.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates unauthenticated network reachability, but the Patchstack reference title mentions authenticated SQL injection, so access requirements should be verified against vendor details.
Researcher notes
The provided sources establish affected product, version range, CWE, and CVSS severity. They do not provide exploit details, active exploitation evidence, or a confirmed patched version in the bundle. There is an apparent access-requirement mismatch between CVSS PR:N and Patchstack’s referenced title.
Mitigation direction
- Inventory WordPress sites for plugin slug paytm-payments and versions through 2.7.3.
- Check Paytm, WordPress plugin, and Patchstack guidance for a fixed version or workaround.
- Prioritize removing or disabling the affected plugin where no trusted fix is available.
- Review database and application logs for suspicious activity around payment plugin endpoints.
- Back up affected sites before remediation and preserve logs for investigation.
Validation and detection
- Confirm whether paytm-payments is installed, active, and at version 2.7.3 or earlier.
- Verify exposure on internet-facing WordPress sites before internal-only systems.
- Compare local findings with the CVE Program and Patchstack entries.
- Check whether vendor guidance identifies authentication requirements or vulnerable endpoints.
- After remediation, confirm the vulnerable plugin version is no longer active.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupDatabase behavior lookup
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.
Open ATT&CK lookupCVE-2022-45805 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.