WordPress plugin
Post Flagger security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High0
- Medium1
- Low0
All Post Flagger vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.4 | Authenticated (Contributor+) Stored Cross-Site Scripting via 'slug' Shortcode Attribute ≤1.1No patch available | CVE-2026-1854 |
- Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting via 'slug' Shortcode Attribute
≤1.1No patch available
Post Flagger: common questions
Does Post Flagger have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in Post Flagger: 1 medium. At least one is not fixed in the latest version.
How do I check which version of Post Flagger I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Post Flagger vulnerability?
CVE-2026-1854, published Mar 20, 2026: Post Flagger <= 1.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'slug' Shortcode Attribute. Severity: Medium (CVSS 6.4).
Is any Post Flagger vulnerability listed in CISA KEV?
No. None of the known Post Flagger vulnerabilities is currently listed in the CISA KEV catalog.