WordPress theme
NeoBeat - Music WordPress Theme security & vulnerabilities
No known unpatched vulnerabilities in the latest version
All 2 known vulnerabilities are fixed in the latest release. If you run an older version, update to null or newer.
- Critical0
- High2
- Medium0
- Low0
All NeoBeat - Music WordPress Theme vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High8.1 | Music WordPress Theme <= 1.7 - Unauthenticated PHP Object Injection ≤1.7Update to 1.8 | CVE-2026-39557 | |
| High8.1 | Unauthenticated Local File Inclusion ≤1.2Update to 1.7 | CVE-2026-22511 |
- High8.1Music WordPress Theme <= 1.7 - Unauthenticated PHP Object Injection
≤1.7Update to 1.8
- High8.1Unauthenticated Local File Inclusion
≤1.2Update to 1.7
NeoBeat - Music WordPress Theme: common questions
Does NeoBeat - Music WordPress Theme have known vulnerabilities?
Yes. VulnCrest Radar lists 2 known vulnerabilities in NeoBeat - Music WordPress Theme: 2 high. None are known to affect version null.
How do I check which version of NeoBeat - Music WordPress Theme I run?
In wp-admin open Appearance → Themes and select the theme; 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 NeoBeat - Music WordPress Theme vulnerability?
CVE-2026-39557, published Apr 8, 2026: NeoBeat - Music WordPress Theme <= 1.7 - Unauthenticated PHP Object Injection. Severity: High (CVSS 8.1).
Is any NeoBeat - Music WordPress Theme vulnerability listed in CISA KEV?
No. None of the known NeoBeat - Music WordPress Theme vulnerabilities is currently listed in the CISA KEV catalog.