# CVE-2024-1587: Newsmatic <= 1.3.4 - Unauthenticated Information Exposure via newsmatic_filter_posts_load_tab_content

> Unauthenticated attackers can view draft posts and post content in the Newsmatic WordPress theme due to missing authorization checks.

- **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:** 9 Apr 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-pp2r-p867-hj9h

## What is CVE-2024-1587?

CVE-2024-1587 is a medium-severity vulnerability in blazethemes Newsmatic, published on 9 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Newsmatic theme for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.3.0 via the 'newsmatic_filter_posts_load_tab_content'. This makes it possible for unauthenticated attackers to view draft posts and post content.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Blazethemes Newsmatic.

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

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

## Is CVE-2024-1587 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1587 is a medium-severity vulnerability in blazethemes Newsmatic, published on 9 Apr 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-1587 in the wild and no public exploit code.

Affected product: blazethemes Newsmatic. 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-1587/ (Markdown: https://insights.sbomify.com/CVE-2024-1587/index.md)
```

## Sources

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

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