subscribe to comments reloaded vulnerabilities and fixes

Recent CVEs affecting subscribe to comments reloaded, with upgrade or downgrade steps. 3 tracked.

Also searched as: subscribetocommentsreloaded.

subscribe to comments reloaded has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2024-04-10. Highest priority: CVE-2014-2274 (score 51/100).

• CVE-2024-31249 MEDIUM 5.3 UPGRADE Insertion of Sensitive Information into Log File vulnerability in WPKube Subscribe To Comments Reloaded.This i
• CVE-2022-29414 MEDIUM 5.4 UPGRADE Multiple (13x) Cross-Site Request Forgery (CSRF) vulnerabilities in WPKube's Subscribe To Comments Reloaded pl
• CVE-2014-2274 HIGH 8.8 UPGRADE Cross-site request forgery (CSRF) vulnerability in the Subscribe To Comments Reloaded plugin before 140219 for

FAQ

How do I fix subscribe to comments reloaded vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is subscribe to comments reloaded being exploited right now?

None of the tracked subscribe to comments reloaded CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which subscribe to comments reloaded CVE should I patch first?

CVE-2014-2274 currently ranks highest (51/100): Cross-site request forgery (CSRF) vulnerability in the Subscribe To Comments Reloaded plugin before 140219 for.

RSS feed for subscribe to comments reloaded · ← Back to latest CVEs