LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47651: WordPress WP Links Page Plugin <= 4.9.4 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Robert Macchi WP Links Page.This issue affects WP Links Page: from n/a through 4.9.4.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-47651 is a CSRF issue in the WordPress WP Links Page plugin through version 4.9.4. An attacker may be able to trick a logged-in user into making an unintended low-impact change. It is medium severity, not listed in CISA KEV, and the provided sources do not confirm active exploitation.

Executive priority

Treat as a moderate web application hygiene item. Prioritize internet-facing WordPress sites where the plugin is active, especially if link-management changes affect brand trust, customer navigation, or compliance-controlled content.

Technical view

The CVE describes CWE-352 Cross-Site Request Forgery in Robert Macchi WP Links Page for WordPress, affecting versions through 4.9.4. CVSS 3.1 is 4.3 with network access, low complexity, no attacker privileges, required user interaction, unchanged scope, and low integrity impact only.

Likely exposure

Exposure is limited to WordPress sites with the WP Links Page plugin installed at version 4.9.4 or earlier. Sites not using this plugin are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not cite active exploitation or a public exploit, and KEV is false. CSRF normally depends on social engineering a logged-in user into a browser action; exact affected actions are not detailed in the provided evidence.

Researcher notes

Evidence is sparse. The CVE and Patchstack reference identify CSRF and affected versions through 4.9.4, but the bundle does not specify vulnerable endpoints, nonce behavior, required victim role, patch version, or proof-of-concept status.

Mitigation direction

  • Inventory WordPress sites for WP Links Page and record installed versions.
  • Check vendor or Patchstack guidance for a fixed version or official workaround.
  • If business permits, disable or remove the plugin until remediation is confirmed.
  • Limit WordPress admin access and avoid persistent admin sessions on untrusted browsing paths.
  • Monitor for unexpected WP Links Page configuration or content changes.

Validation and detection

  • Confirm whether WP Links Page is installed on each WordPress site.
  • Verify whether any installed version is 4.9.4 or earlier.
  • Review WordPress audit logs for unexpected plugin-related administrative changes.
  • Check vendor release notes before marking an upgrade as remediation.
  • Document any sites where the plugin is required and cannot be disabled.
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-47651 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
4.3 (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: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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2023-47651Attack 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: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
Robert MacchiWP Links Pagewp-links-page, 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.