# CVE-2023-6962: WP Meta SEO <= 4.5.12 - Information Exposure via Meta Description

> Unauthenticated attackers can access sensitive information from meta descriptions of password-protected posts in the WP Meta SEO plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-qrcv-jf73-5vrq

## What is CVE-2023-6962?

CVE-2023-6962 is a medium-severity vulnerability in joomunited WP Meta SEO, published on 2 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Meta SEO plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.5.12 via the meta description. This makes it possible for unauthenticated attackers to disclose potentially sensitive information via the meta description of password-protected posts.

Weakness: CWE-922 (Insecure Storage of Sensitive Information), CWE-1230 (Exposure of Sensitive Information Through Metadata)

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

It affects 1 product.


Products: Joomunited Wp Meta Seo.

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

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

## Is CVE-2023-6962 being exploited?

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

## Other vulnerabilities in joomunited WP Meta SEO

- [CVE-2023-1381](https://insights.sbomify.com/CVE-2023-1381/): WP Meta SEO < 4.5.5 - Author+ PHAR Deserialization (high 8.8)
- [CVE-2023-0875](https://insights.sbomify.com/CVE-2023-0875/): WP Meta SEO < 4.5.3 - Subscriber+ SQLi (high 8.8)
- [CVE-2023-6961](https://insights.sbomify.com/CVE-2023-6961/): WP Meta SEO <= 4.5.12 - Unauthenticated Stored Cross-Site Scripting via Referer header (high 7.2)
- [CVE-2024-45456](https://insights.sbomify.com/CVE-2024-45456/): WordPress WP Meta SEO plugin <= 4.5.13 - Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2023-0876](https://insights.sbomify.com/CVE-2023-0876/): WP Meta SEO < 4.5.3 - Subscriber+ Improper Authorization causing Arbitrary Redirect (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-6962 is a medium-severity vulnerability in joomunited WP Meta SEO, published on 2 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-6962 in the wild and no public exploit code.

Affected product: joomunited WP Meta SEO. 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-6962/ (Markdown: https://insights.sbomify.com/CVE-2023-6962/index.md)
```

## Sources

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

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