WordPress plugin
My Default Post Content 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 My Default Post Content vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium4.4 | Authenticated (Administrator+) Stored Cross-Site Scripting ≤0.7.3No patch available | CVE-2025-30573 |
- Medium4.4Authenticated (Administrator+) Stored Cross-Site Scripting
≤0.7.3No patch available
My Default Post Content: common questions
Does My Default Post Content have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in My Default Post Content: 1 medium. At least one is not fixed in the latest version.
How do I check which version of My Default Post Content 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 My Default Post Content vulnerability?
CVE-2025-30573, published Mar 24, 2025: My Default Post Content <= 0.7.3 - Authenticated (Administrator+) Stored Cross-Site Scripting. Severity: Medium (CVSS 4.4).
Is any My Default Post Content vulnerability listed in CISA KEV?
No. None of the known My Default Post Content vulnerabilities is currently listed in the CISA KEV catalog.