# CVE-2026-78149: Information disclosure in Smart Post

> Unauthenticated attackers can read password-protected post content and the stored password via an AJAX action in the Smart Post 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 Sep 2026
- **Updated:** 6 Sep 2026
- **Also known as:** GHSA-x6q5-5p66-45w5

## What is CVE-2026-78149?

CVE-2026-78149 is a medium-severity vulnerability in Unknown Smart Post, published on 5 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Smart Post  WordPress plugin before 4.0.8 does not check whether a post is password protected before returning its content and its stored password through an unauthenticated AJAX action, allowing unauthenticated users to read protected post content and the password that guards it.

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

## Which versions are affected by CVE-2026-78149?


## How do I fix CVE-2026-78149?

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

## Is CVE-2026-78149 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-78149 and fix it if it is affected.

What it is: CVE-2026-78149 is a medium-severity vulnerability in Unknown Smart Post, published on 5 Sep 2026. 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-2026-78149 in the wild and no public exploit code.

Affected product: Unknown Smart 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-2026-78149/ (Markdown: https://insights.sbomify.com/CVE-2026-78149/index.md)
```

## Sources

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

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