Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

wp content source control vulnerabilities and fixes

Recent CVEs affecting wp content source control, with upgrade or downgrade steps. 1 tracked.

Also searched as: wpcontentsourcecontrol.

wp content source control has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2014-08-22. Highest priority: CVE-2014-5368 (score 47/100).

FAQ

How do I fix wp content source control 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 wp content source control being exploited right now?

None of the tracked wp content source control CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which wp content source control CVE should I patch first?

CVE-2014-5368 currently ranks highest (47/100): Directory traversal vulnerability in the file_get_contents function in downloadfiles/download.php in the WP Co.

← Back to latest CVEs