dbcve.org
Payment GatewayWordPress extension · Paytm

CVE-2022-45362

MEDIUM · 6.5 CVSS v3.1 Published 2023-12-07
Fix available
A fix is available. Upgrade to after 2.7.0 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Server-Side Request Forgery (SSRF) vulnerability in Paytm Paytm Payment Gateway.This issue affects Paytm Payment Gateway: from n/a through 2.7.0.

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 confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in the Paytm Payment Gateway plugin versions up to 2.7.0. The vulnerability allows an attacker to make the server perform requests to internal or external resources, potentially accessing internal services, cloud metadata endpoints, or bypassing network restrictions.

MitigationImplement strict URL validation with allowlists, restrict outbound network requests, and disable unnecessary URL-following capabilities in HTTP client libraries.

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
Affected:<= 2.7.0

CVSS 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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Paytm Payment Gateway plugin is installed
    Check for the plugin directory at wp-content/plugins/paytm-payment-gateway/ or list all installed plugins via wp plugin list (if wp-cli available) or inspect the WordPress plugins admin page.
    Affected if The Paytm Payment Gateway plugin directory or entry exists in the WordPress installation.
  2. Determine the installed version of Paytm Payment Gateway
    Open the main plugin file (paytm-payment-gateway.php) or readme.txt in the plugin directory and locate the version comment/header, or use grep to search for 'Version:' within the plugin files.
    Affected if The reported version number is 2.7.0 or lower (e.g., 2.7.0, 2.6.5, 2.5.0).
  3. Verify the vulnerable URL-fetching functionality exists
    Search the plugin source code for functions that perform HTTP requests, such as calls to wp_remote_get, wp_remote_post, file_get_contents with URLs, or curl_exec with URLs passed from user input. Examine the payment processing logic where merchant or callback URLs are handled.
    Affected if The plugin contains code that fetches URLs (especially from callback parameters or API endpoints) without strict validation, which would be the SSRF vector.

A user is affected if the Paytm Payment Gateway plugin version is 2.7.0 or lower AND the vulnerable URL-handling code path is present and accessible to untrusted input sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.7.0
Interim mitigation

Implement strict URL validation with allowlists, restrict outbound network requests, and disable unnecessary URL-following capabilities in HTTP client libraries.

Recommended fix Moderate confidence

Upgrade to Paytm Payment Gateway version 2.7.1 or later (latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Paytm Payment Gateway plugin
  4. Check if an update is available (should show version higher than 2.7.0)
  5. If update available, click 'Update Now' to upgrade to the latest stable version
  6. If no automatic update appears, manually download the latest version from the WordPress plugin repository or contact Paytm support
  7. After upgrade, verify the new version number in the plugins list

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Payment Gateway Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45362 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-45362 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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