LiveActive security incident?Get immediate response
CVE Record

CVE-2021-39308: WooCommerce myghpay Payment Gateway <= 3.0 Reflected Cross-Site Scripting

The WooCommerce myghpay Payment Gateway WordPess plugin is vulnerable to Reflected Cross-Site Scripting via the clientref parameter found in the ~/processresponse.php file which allows attackers to inject arbitrary web scripts, in versions up to and including 3.0.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-39308 affects the WooCommerce myghpay Payment Gateway WordPress plugin through version 3.0. A crafted link could make a visitor’s browser run attacker-supplied script if the user follows it. Business impact is usually limited, but it can expose session data or alter page content in a payment-related WordPress context.

Executive priority

Treat this as a moderate-priority web exposure, especially for e-commerce sites using this payment gateway. It is not confirmed actively exploited in the supplied evidence, but payment-page XSS can affect customer trust and should not remain unresolved.

Technical view

The issue is reflected cross-site scripting in the clientref parameter handled by processresponse.php. It is unauthenticated but requires user interaction. CVSS 3.1 is 6.1 with network attack vector, low complexity, changed scope, and low confidentiality and integrity impact.

Likely exposure

Exposure is limited to WordPress sites running WooCommerce myghpay Payment Gateway version 3.0 or earlier. The source bundle does not identify other affected products, CPEs, or a confirmed fixed version.

Exploitation context

The CVE is not listed as CISA KEV in the provided data, and the bundle gives no evidence of active exploitation. Exploitation would depend on convincing a user to open a maliciously crafted payment response URL.

Researcher notes

The key evidence is the CVE description and WordPress Trac reference to processresponse.php. The provided sources establish affected versions through 3.0 and reflected XSS via clientref, but do not provide exploit telemetry, CISA KEV status, or a confirmed patched version.

Mitigation direction

  • Inventory WordPress sites for the affected WooCommerce myghpay Payment Gateway plugin.
  • Check vendor, WordPress plugin, or Wordfence guidance for a fixed or retired release.
  • Disable or remove the plugin where it is not business-critical.
  • Use WAF or application filtering as temporary risk reduction for reflected XSS patterns.
  • Prioritize replacement if no maintained fixed version is available.

Validation and detection

  • Confirm whether any site runs WooCommerce myghpay Payment Gateway version 3.0 or earlier.
  • Review plugin files for processresponse.php and handling of the clientref parameter.
  • Check web logs for unusual requests to processresponse.php.
  • Verify payment workflows still function after plugin update, removal, or replacement.
  • Document any compensating controls if a fixed version cannot be confirmed.
Prepared
Confidence
high
Sources
4

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-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookup
cve · low confidence lookup

CVE-2021-39308 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2021-39308Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WooCommerce myghpay Payment GatewayWooCommerce myghpay Payment Gateway3.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.