plugin

Mycurator Vulnerabilities

3 known security issues reported for the Mycurator WordPress plugin. Most recent disclosed Nov 1, 2024.

3 medium

Running Mycurator on your site? Check whether your installed version is affected.

Scan your site free

MyCurator Content Curation <= 3.78 - Authenticated (Editor+) Stored Cross-Site Scripting

medium

The MyCurator Content Curation plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 3.78 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with editor-level access and above, to inject arbitrary web scripts in p...

CVSS:
4.4
Affected:
up to 3.78
Fixed in:
3.79
Disclosed:
Nov 1, 2024

CVE-2024-51668 on NVD →

MyCurator Content Curation <= 3.76 - Reflected Cross-Site Scripting

medium

The MyCurator Content Curation plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'topic' parameter in all versions up to, and including, 3.76 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pag...

CVSS:
6.1
Affected:
up to 3.76
Fixed in:
3.77
Disclosed:
Mar 18, 2024

CVE-2024-29139 on NVD →

MyCurator Content Curation <= 3.74 - Cross-Site Request Forgery

medium

The MyCurator Content Curation plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.74. This is due to missing or incorrect nonce validation on the mct_ai_logspage() function. This makes it possible for unauthenticated attackers to filter and reset logs via a forged reque...

CVSS:
4.3
Affected:
up to 3.74
Fixed in:
3.75
Disclosed:
Jun 22, 2023

CVE-2023-32104 on NVD →

Protect your WordPress site

Run a free security scan to detect vulnerable plugins and themes, exposed files, and malware — no plugin install, no signup.

Scan your site free

← Back to the vulnerability database