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

> Attackers can trick users into performing unintended actions in the Vertical scroll recent post WordPress plugin.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Nov 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-9mcp-r979-67vc

## What is CVE-2023-47671?

CVE-2023-47671 is a medium-severity vulnerability in Gopi Ramasamy Vertical scroll recent post, published on 18 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2023-47671?

It affects 1 product.


Products: Gopiplus Vertical Scroll Recent Registered User.

## How do I fix CVE-2023-47671?

No fix has been published for CVE-2023-47671 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-47671 being exploited?

There is no known exploitation of CVE-2023-47671 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-47671 and fix it if it is affected.

What it is: CVE-2023-47671 is a medium-severity vulnerability in Gopi Ramasamy Vertical scroll recent post, published on 18 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-47671 in the wild and no public exploit code.

Affected product: Gopi Ramasamy Vertical scroll recent post. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-47671/ (Markdown: https://insights.sbomify.com/CVE-2023-47671/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-47671
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-47671
- OSV: https://osv.dev/vulnerability/CVE-2023-47671

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-47671/
Summaries are generated and may contain mistakes; the official description above is the record.