3 ms·

citation needed

• johansch 11y ago
  http://www.cvedetails.com/vulnerability-list/vendor_id-2337/product_id-4096/ http://www.cvedetails.com/vulnerability-list/vendor_id-2337/...
  • Karunamon 11y ago
    200 vulns in 11 years? That doesn't sound awful in perspective. I bet you use software every single day that has significantly more.
• belorn 11y ago
  The problem with wordpress security is mostly attached the insecure developer practices when dealing with themes. Many developers just take a standard theme, copies it, and then attach their own modifications. This piece of code never gets updated and the owner rarely even know that its there until they get hacked, reinstall with a updated wordpress, and then get rehacked a few days later.
  • pknight 11y ago
    Themes rarely have hackable exploits due to what they (are supposed to) do. If there's insecure code in there it's probably code with functionality that belongs in a plugin to start with. Themes that have had vulnerabilities in them tend to be the kinds of commercial themes that are filled with features and 3rd party scripts to satiate users demands. Not really a WordPress core problem, it is a market problem. Although package management is something WordPress lacks in.