LiveActive security incident?Get immediate response
CVE Record

CVE-2023-45638: WordPress Eupago Gateway For Woocommerce Plugin <= 3.1.9 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in euPago Eupago Gateway For Woocommerce plugin <= 3.1.9 versions.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-45638 is a CSRF issue in the WordPress Eupago Gateway For Woocommerce plugin through version 3.1.9. An attacker would need to trick an authenticated user into taking an action, but the listed impact is high integrity risk, meaning settings or transaction-related state could be changed without intended authorization.

Executive priority

Treat this as a moderate-priority e-commerce platform risk. It is not documented as actively exploited in the supplied sources, but affected payment gateway plugins deserve prompt inventory, version review, and vendor-guided remediation because integrity impact is high.

Technical view

The supplied CVE data describes CWE-352 Cross-Site Request Forgery affecting euPago Eupago Gateway For Woocommerce <= 3.1.9. CVSS 3.1 is 6.5 with network attack vector, low complexity, no privileges, required user interaction, no confidentiality or availability impact, and high integrity impact. No exploit details or fixed version are provided in the bundle.

Likely exposure

Exposure is likely limited to WordPress/WooCommerce sites that installed the euPago payment gateway plugin at version 3.1.9 or earlier. Sites not using this specific plugin are not indicated as affected by the supplied sources.

Exploitation context

The bundle does not show CISA KEV inclusion or other evidence of active exploitation. Successful abuse requires user interaction, consistent with CSRF, and would target actions available to an authenticated browser session.

Researcher notes

Evidence is sparse. The sources identify product, weakness class, CVSS vector, and affected ceiling, but do not include endpoint details, proof of concept, exploit telemetry, or a fixed version. Avoid assuming exploitability beyond the CSRF class and stated CVSS properties.

Mitigation direction

  • Inventory WordPress sites for the Eupago Gateway For Woocommerce plugin.
  • Check installed versions and flag 3.1.9 or earlier.
  • Review vendor or Patchstack guidance for a fixed release or official mitigation.
  • Disable or remove the plugin where business impact permits until guidance is confirmed.
  • Restrict administrative access and enforce anti-phishing controls for WordPress operators.

Validation and detection

  • Confirm whether each WooCommerce site uses package eupago-gateway-for-woocommerce.
  • Record the installed plugin version on every affected WordPress instance.
  • Review plugin changelog or vendor advisory for CSRF remediation confirmation.
  • Check whether payment gateway settings changed unexpectedly around relevant dates.
  • Verify administrative users are protected with MFA and least privilege.
Prepared
Confidence
medium
Sources
3

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-352: 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-2023-45638 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.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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
2Source 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.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2023-45638Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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
euPagoEupago Gateway For Woocommerceeupago-gateway-for-woocommerce, n/aunaffected
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.