LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47671: WordPress Vertical scroll recent post Plugin <= 14.0 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Gopi Ramasamy Vertical scroll recent.This issue affects Vertical scroll recent post: from n/a through 14.0.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A WordPress plugin used to display recent posts has a CSRF flaw through version 14.0. If an administrator is tricked into interacting with a malicious page, an attacker may cause unintended plugin-related changes. The provided sources do not identify stolen data or confirmed exploitation.

Executive priority

Treat this as a routine but real WordPress maintenance risk. It is not a critical emergency based on the supplied evidence, but vulnerable plugins can enable unauthorized site changes when administrators are tricked. Prioritize inventory, update checks, and removal decisions.

Technical view

CVE-2023-47671 is a CWE-352 Cross-Site Request Forgery issue in Gopi Ramasamy Vertical scroll recent post. CVSS 3.1 is 5.4 with network attack vector, low complexity, no privileges required, and user interaction required. Impact is limited integrity and availability; confidentiality impact is none.

Likely exposure

Exposure is limited to WordPress sites running Vertical scroll recent post through version 14.0. Risk is higher where administrators are regularly logged in and may browse attacker-controlled content. The source bundle does not provide install counts, vulnerable endpoint details, or environment-specific prerequisites.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The attack requires user interaction, consistent with CSRF. Public evidence provided here is not enough to assess exploit maturity or real-world targeting.

Researcher notes

The bundle provides high-level CVE and Patchstack references but not the exact affected action, nonce failure location, patch commit, or fixed version. Avoid asserting exploitability beyond CSRF-driven unintended state change until vendor details or code review confirms the vulnerable flow.

Mitigation direction

  • Inventory WordPress sites for vertical-scroll-recent-post versions through 14.0.
  • Check vendor, WordPress plugin, and Patchstack guidance for fixed or removed versions.
  • Update the plugin if an official fixed release is available.
  • Disable or remove the plugin if no maintained fixed release is available.
  • Limit WordPress administrator sessions to trusted browsing contexts.

Validation and detection

  • Confirm whether the plugin is installed and active on each WordPress site.
  • Record the installed plugin version and compare it with the affected range.
  • Review recent plugin setting changes made by administrator accounts.
  • Check security advisories for any newly published fix or mitigation.
  • Verify compensating controls do not rely on unsupported assumptions.
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-47671 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-47671Attack 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
Gopi RamasamyVertical scroll recent postvertical-scroll-recent-post, 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.