# CVE-2025-48311: WordPress Invisible Optin plugin <= 1.0 - Cross Site Request Forgery (CSRF) to Stored XSS vulnerability

> Attackers can inject malicious scripts via CSRF, leading to stored XSS and potential account takeover in the Invisible Optin WordPress plugin.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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:** 28 Aug 2025
- **Updated:** 12 May 2026
- **Also known as:** GHSA-76wp-4fj2-5hg4

## What is CVE-2025-48311?

CVE-2025-48311 is a high-severity cross-site scripting vulnerability in OffClicks Invisible Optin, published on 28 Aug 2025. 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 OffClicks Invisible Optin invisible-optin allows Stored XSS.This issue affects Invisible Optin: from n/a through <= 1.0.

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

## Which versions are affected by CVE-2025-48311?


## How do I fix CVE-2025-48311?

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

## Is CVE-2025-48311 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-48311 and fix it if it is affected.

What it is: CVE-2025-48311 is a high-severity cross-site scripting vulnerability in OffClicks Invisible Optin, published on 28 Aug 2025. 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-2025-48311 in the wild and no public exploit code.

Affected product: OffClicks Invisible Optin. 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-2025-48311/ (Markdown: https://insights.sbomify.com/CVE-2025-48311/index.md)
```

## Sources

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

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