LiveActive security incident?Get immediate response
CVE Record

CVE-2023-51485: WordPress Pay with Vipps for WooCommerce Plugin <= 1.14.13 is vulnerable to Cross Site Scripting (XSS)

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WP Hosting Pay with Vipps and MobilePay for WooCommerce allows Stored XSS.This issue affects Pay with Vipps and MobilePay for WooCommerce: from n/a through 1.14.13.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a stored cross-site scripting issue in a WordPress WooCommerce payment plugin. A lower-privileged user could save unsafe input that later runs in another user's browser after interaction. For affected commerce sites, the main concern is admin-session abuse, data exposure, or transaction workflow tampering within the WordPress context.

Executive priority

Treat as a near-term remediation item for affected WooCommerce stores, especially where many staff or partners can access WordPress. It is not marked as actively exploited in the provided evidence, but stored XSS in commerce administration can still create meaningful business risk.

Technical view

CVE-2023-51485 is CWE-79 in WP Hosting Pay with Vipps and MobilePay for WooCommerce, affecting versions through 1.14.13. The CVSS 3.1 score is 6.5 with network attack vector, low complexity, low privileges required, user interaction required, and changed scope.

Likely exposure

Exposure is limited to WordPress/WooCommerce sites using the Pay with Vipps and MobilePay for WooCommerce plugin at version 1.14.13 or earlier.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The issue is stored XSS, so attacker-controlled content must be saved in an affected workflow and later viewed or triggered by another user.

Researcher notes

Evidence is sparse in the supplied bundle. It identifies the vulnerability class, CVSS vector, affected plugin, and version ceiling, but does not provide detailed vulnerable parameters, proof of exploitation, or a named fixed version. Avoid assuming exploit maturity or patch details beyond vendor guidance.

Mitigation direction

  • Inventory WordPress sites for the woo-vipps plugin and its installed version.
  • Update affected installations when vendor or Patchstack guidance identifies a fixed release.
  • If no fix is confirmed, review vendor guidance before changing production behavior.
  • Limit plugin administration to trusted users until remediation is complete.
  • Monitor WordPress admin activity for unexpected content or settings changes.

Validation and detection

  • Confirm whether Pay with Vipps and MobilePay for WooCommerce is installed.
  • Record plugin versions and flag installations at 1.14.13 or earlier.
  • Review plugin-related roles and workflows that accept stored user input.
  • Check logs for unusual admin activity after plugin-related page views.
  • Verify remediation against vendor guidance after updating or compensating controls.
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-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-2023-51485 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:L/UI:R/S:C/C:L/I:L/A:L

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:L/UI:R/S:C/C:L/I:L/A:L2.33.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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
WP HostingPay with Vipps and MobilePay for WooCommercewoo-vipps, n/aunaffected
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.