LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38341: WooCommerce Payment Gateway Per Category <= 2.0.10 Reflected Cross-Site Scripting

The WooCommerce Payment Gateway Per Category WordPress plugin is vulnerable to Reflected Cross-Site Scripting due to a reflected $_SERVER["PHP_SELF"] value in the ~/includes/plugin_settings.php file which allows attackers to inject arbitrary web scripts, in versions up to and including 2.0.10.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability affects a WordPress WooCommerce plugin and could let an attacker make a victim’s browser run attacker-controlled script after clicking a crafted link. It is not listed as known exploited, but it can affect customer trust and administrative sessions if exposed on a live site.

Executive priority

Treat as a moderate web application risk. Prioritize internet-facing WooCommerce sites and administrator-heavy environments first. The main business concern is session or trust impact from XSS, not direct server takeover based on the supplied evidence.

Technical view

CVE-2021-38341 is a CWE-79 reflected cross-site scripting issue in WooCommerce Payment Gateway Per Category through 2.0.10. The reported cause is reflection of the PHP_SELF server value in includes/plugin_settings.php. CVSS 3.1 is 6.1, with network access, low complexity, no privileges, and required user interaction.

Likely exposure

Exposure is likely limited to WordPress sites running the WooCommerce Payment Gateway Per Category plugin at version 2.0.10 or earlier. The bundle does not identify affected CPEs, a fixed version, or whether vulnerable code is reachable without administrative context.

Exploitation context

The CVSS vector requires user interaction, consistent with reflected XSS. The source bundle and KEV status do not support active exploitation claims. Practical risk depends on whether an attacker can get a site user or administrator to open a crafted URL.

Researcher notes

Evidence identifies the vulnerable plugin, version boundary, CWE, CVSS vector, and vulnerable file reference. The bundle does not name a fixed version, patch commit, exploitation in the wild, or detailed reachability conditions, so validation should stay source-grounded.

Mitigation direction

  • Inventory WordPress sites for this plugin and version 2.0.10 or earlier.
  • Check WordPress plugin or vendor guidance for a fixed release before upgrading.
  • Disable or remove the plugin where it is unnecessary or unsupported.
  • Restrict administrative access and reinforce phishing-resistant controls for WordPress administrators.

Validation and detection

  • Confirm installed plugin name and version on each WooCommerce site.
  • Review whether includes/plugin_settings.php exists in deployed plugin code.
  • Check security monitoring for suspicious requests involving the plugin settings path.
  • Document any compensating controls if no vendor fix is available.
Prepared
Confidence
medium
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-38341 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-38341Attack 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 Payment Gateway Per CategoryWooCommerce Payment Gateway Per Category2.0.10Listed
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.