WordPress plugin
Be Shortcodes 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 Be Shortcodes vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.4 | Authenticated (Contributor+) Stored Cross-Site Scripting ≤1.0.0No patch available | CVE-2024-51881 |
- Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
≤1.0.0No patch available
Be Shortcodes: common questions
Does Be Shortcodes have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in Be Shortcodes: 1 medium. At least one is not fixed in the latest version.
How do I check which version of Be Shortcodes 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 Be Shortcodes vulnerability?
CVE-2024-51881, published Nov 8, 2024: Be Shortcodes <= 1.0.0 - Authenticated (Contributor+) Stored Cross-Site Scripting. Severity: Medium (CVSS 6.4).
Is any Be Shortcodes vulnerability listed in CISA KEV?
No. None of the known Be Shortcodes vulnerabilities is currently listed in the CISA KEV catalog.