Mg12's vulnerability footprint centers on WordPress plugin products, notably wp-recentcomments, with observed weaknesses rooted in improper input neutralization during web page generation and SQL command construction. These application-layer input-handling issues reflect the parsing demands typical of plugins that process and display user-contributed data; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Mg12 over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2012-1067HIGH SQL injection vulnerability in the WP-RecentComments plugin 2.0.7 for WordPress allows remote attackers to execute arbitrary SQL commands via the id parameter in an rc-content acti | Feb 14, 2012 | 7.5 | 22 | NO | NO |
CVE-2023-23886MEDIUM Missing Authorization vulnerability in mg12 WP-RecentComments allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP-RecentComments: from n/a | Dec 9, 2024 | 5.4 | 17 | NO | NO |
CVE-2012-1068MEDIUM Cross-site scripting (XSS) vulnerability in the rc_ajax function in core.php in the WP-RecentComments plugin before 2.0.7 for WordPress allows remote attackers to inject arbitrary | Feb 14, 2012 | 4.3 | 16 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Mg12.
Media articles that mention a CVE ID that affects a product developed by Mg12 — matched by CVE ID, not by vendor name.