Payment GatewayWordPress extension · Paytm
CVE-2022-45805
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Paytm Paytm Payment Gateway paytm-payments allows SQL Injection.This issue affects Paytm Payment Gateway: from n/a through 2.7.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in Paytm Payment Gateway plugin allows attackers to inject malicious SQL commands through unsanitized user inputs, potentially enabling unauthorized database access, data exfiltration, or complete system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Payment GatewayWordPress extension
<= 2.7.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Paytm Payment Gateway plugin installationCheck your WordPress installation at wp-content/plugins/paytm-payment-gateway/ for the plugin directory and main plugin file (usually paytm.php)Affected if The plugin directory does not exist or the plugin is not installed, then you are not affected by this CVE
-
Identify the installed plugin versionOpen the main plugin PHP file and locate the plugin header comment which contains the Version field (for example: /* Plugin Name: Paytm Payment Gateway Version: x.x.x */)Affected if The version number displayed is 2.7.3 or lower (for example: 2.7.0, 2.7.1, 2.7.2, 2.7.3), indicating you are running an affected version
-
Verify the plugin is activeLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins, or query the WordPress database table wp_options for the option_name 'active_plugins'Affected if The plugin appears in the list of active plugins and the version check in step 2 shows an affected version, then your environment is vulnerable
-
Inspect database query handling (optional code review)Review the main plugin PHP files for direct SQL queries that use user-supplied input (such as $_POST, $_GET, or $_REQUEST variables) without parameterized queries or prepared statementsAffected if The code contains unsanitized user inputs passed directly to SQL queries, confirming the SQL injection vulnerability is present in your specific installation
Your environment is affected if the Paytm Payment Gateway plugin is installed, active, and running version 2.7.3 or lower, which contains unsanitized SQL input handling.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement parameterized queries/prepared statements for all database operations, apply proper input validation and escaping, and update to a patched version beyond 2.7.3.
Fix this in Payment Gateway
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45805 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-45805 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data