Security readout for executives and security teams
Plain-English summary
This flaw affects the WordPress Paytm Payment Gateway plugin through version 2.7.0. An unauthenticated attacker may be able to make the website server send requests on their behalf, creating SSRF risk. The provided sources do not show confirmed active exploitation or a named fixed version.
Executive priority
Prioritize quickly for WordPress payment sites using Paytm, because the vulnerable component sits in an internet-facing commerce workflow. If the plugin is not deployed, business urgency is low.
Technical view
CVE-2022-45362 is a CWE-918 SSRF in Paytm Payment Gateway for WordPress, reported as affecting versions through 2.7.0. CVSS 3.1 is 7.2 with network attack vector, low complexity, no privileges, no user interaction, changed scope, and low confidentiality and integrity impact.
Likely exposure
Exposure is limited to WordPress sites with the Paytm Payment Gateway plugin installed, especially versions 2.7.0 or earlier. Sites not using this plugin are not directly exposed based on the provided bundle.
Exploitation context
The CVE is not listed as KEV in the supplied data. No cited source in the bundle confirms active exploitation, public exploit availability, or real-world targeting. Treat exploit status as unconfirmed.
Researcher notes
Evidence is limited to the CVE metadata and Patchstack reference. The bundle does not identify the vulnerable endpoint, affected code path, fixed release, or exploit telemetry. Avoid assuming broader Paytm product impact beyond the named WordPress plugin.
Mitigation direction
- Inventory WordPress sites for the Paytm Payment Gateway plugin.
- Confirm whether installed versions are 2.7.0 or earlier.
- Check Paytm and Patchstack guidance for supported remediation.
- Disable or remove vulnerable plugin deployments if no safe remediation is available.
- Review outbound request restrictions for WordPress hosting environments.
Validation and detection
- Verify affected sites actually run the Paytm Payment Gateway plugin.
- Record the installed plugin version and operational payment dependency.
- Check CVE and Patchstack entries for updated fix guidance.
- Review web and application logs for unusual server-side outbound requests.
- Confirm the plugin is absent, disabled, or remediated per vendor guidance.
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-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material 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-45362 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
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
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:C/C:L/I:L/A:N3.92.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
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.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.