LiveActive security incident?Get immediate response
CVE Record

CVE-2023-46078: WordPress Serial Numbers for WooCommerce – License Manager Plugin <= 1.6.3 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in PluginEver WC Serial Numbers plugin <= 1.6.3 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability affects the WordPress WC Serial Numbers plugin for WooCommerce through version 1.6.3. A malicious site could trick an already authenticated WordPress user into causing unintended plugin actions. The reported impact is limited, but it can still affect store operations or plugin data integrity.

Executive priority

Treat this as a moderate WordPress plugin risk. It is not described as actively exploited, but WooCommerce licensing workflows can be business-sensitive, so affected stores should verify versions and follow vendor guidance promptly.

Technical view

CVE-2023-46078 is a CWE-352 cross-site request forgery issue in PluginEver WC Serial Numbers. The CVSS 3.1 score is 5.4, with network attack vector, low complexity, no attacker privileges, and required user interaction. The source bundle does not identify a fixed version or specific vulnerable endpoint.

Likely exposure

Exposure is limited to WordPress/WooCommerce sites using PluginEver WC Serial Numbers, especially installations at or below version 1.6.3 with authenticated administrators or store managers using the browser.

Exploitation context

The CVE is not listed as KEV in the source bundle, and no cited source states active exploitation. Practical abuse requires user interaction by an authenticated site user, consistent with CSRF.

Researcher notes

Evidence is thin: the bundle confirms CSRF, affected plugin identity, version threshold, CVSS, and CWE only. It does not provide endpoint details, exploit status, proof-of-concept, fixed version, or remediation specifics.

Mitigation direction

  • Inventory WordPress sites for the wc-serial-numbers plugin.
  • Check installed plugin versions and flag versions at or below 1.6.3.
  • Review PluginEver and Patchstack guidance for a fixed release or mitigation.
  • Update the plugin when a vendor-confirmed safe version is available.
  • Remove or disable the plugin where it is not business-critical.

Validation and detection

  • Confirm whether WC Serial Numbers is installed on each WooCommerce site.
  • Record the installed version and compare it with the 1.6.3 threshold.
  • Review vendor advisory details for fixed-version confirmation.
  • Check whether privileged users reported unexpected plugin changes.
  • Document compensating controls if no vendor fix is available.
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-46078 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
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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
PluginEverWC Serial Numberswc-serial-numbers, 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.