WordPress security by component
Catch Themes Demo Import
Plugin description
Catch Themes Demo Import is a WordPress component with 3 published CVE records in this archive. The latest tracked vulnerability was published Jul 16, 2026; the highest published CVSS base score is 7.2.
Plugin slug:
catch-themes-demo-importLatest vulnerability
CVE-2026-15336: Catch Themes Demo Import: A security weakness
Catch Themes Demo Import is affected by a security weakness. Exploitation requires an authenticated subscriber account. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 3.3. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
| Safe version |
|
||
|---|---|---|---|
| Jul 16, 2026 |
CVE-2026-15336
Catch Themes Demo Import: A security weakness
Catch Themes Demo Import is affected by a security weakness. Exploitation requires an authenticated subscriber account. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 3.3. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE4.3
NVDPending
|
| Mar 07, 2022 |
CVE-2022-0440
Catch Themes Demo Import: A security weakness
Catch Themes Demo Import is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVEPending
NVD7.2
|
| Oct 21, 2021 |
CVE-2021-39352
Catch Themes Demo Import: Dangerous file upload
Catch Themes Demo Import is affected by dangerous file upload. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can place attacker-controlled executable content on the server and may lead to full site compromise. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE7.2
NVD7.2
|