WordPress plugin
MJ Update History 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
- Medium2
- Low0
All MJ Update History vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium4.3 | Missing Authorization ≤1.0.4No patch available | CVE-2024-35671 | |
| Medium6.1 | Reflected Cross-Site Scripting ≤1.0.4No patch available | CVE-2024-32543 |
- Medium4.3Missing Authorization
≤1.0.4No patch available
- Medium6.1Reflected Cross-Site Scripting
≤1.0.4No patch available
MJ Update History: common questions
Does MJ Update History have known vulnerabilities?
Yes. VulnCrest Radar lists 2 known vulnerabilities in MJ Update History: 2 medium. At least one is not fixed in the latest version.
How do I check which version of MJ Update History 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 MJ Update History vulnerability?
CVE-2024-35671, published Jun 3, 2024: MJ Update History <= 1.0.4 - Missing Authorization. Severity: Medium (CVSS 4.3).
Is any MJ Update History vulnerability listed in CISA KEV?
No. None of the known MJ Update History vulnerabilities is currently listed in the CISA KEV catalog.