# CVE-2024-1769: JM Twitter Cards <= 14 - Information Exposure via Meta Description

> Unauthenticated attackers can view password-protected post content via meta description data in the JM Twitter Cards WordPress 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:** 5 Mar 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-9qgv-7wf9-26xp

## What is CVE-2024-1769?

CVE-2024-1769 is a medium-severity vulnerability in jmlapam JM Twitter Cards, published on 5 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The JM Twitter Cards plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 14 via the meta description data. This makes it possible for unauthenticated attackers to view password protected post content when viewing the page source.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-1769?

It affects 1 product.


Products: Jmlapam Jm Twitter Cards.

## How do I fix CVE-2024-1769?

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

## Is CVE-2024-1769 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1769 and fix it if it is affected.

What it is: CVE-2024-1769 is a medium-severity vulnerability in jmlapam JM Twitter Cards, published on 5 Mar 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-2024-1769 in the wild and no public exploit code.

Affected product: jmlapam JM Twitter Cards. 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-2024-1769/ (Markdown: https://insights.sbomify.com/CVE-2024-1769/index.md)
```

## Sources

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

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