36 milions WordPress websites vulnerable to 9 security issues
learnwebdevelopment.review/article/wordpress-...Posted Sep 20, 2017, 3:36 PM UTC
022
learnwebdevelopment.review
A quick websearch reveals that CVE-2017-8295 was fixed in 4.7.5.
2
Not sure what you're searching, but it was not fixed in 4.7.5. Exploit sites just didn't update their info after 4.7.5. The issue still still lingers. Just a tip: For security info look at the WP core code, not Google searches.
0
Not sure what you're searching, but it was not fixed in 4.7.5.
Citation required.
1
0
"WordPress 2.3-4.7.5"
That is what it says on the WPVulnDB website, so you're claiming that their information is false.
In case maybe you don't know how to read that, what that says is it only effects WordPress versions 2.3 through 4.7.5. In other words, it was fixed.
1
Save yourself the wasted click.
WordPress 4.8.2 fixed 9 vulnerabilities - but still refuses to fix CVE-2017-8295
WORDPRESS 4.8.2 COMES WITH FIXES FOR 9 VULNERABILITIES, BUT REFUSES TO FIX CVE-2017-8295 On 19 Sep, 2017, WordPress 4.8.2 was released to the public. Nine high security issues are fixed but Core Team still refuses to fix CVE-2017-8295 - Host Header Attack Vulnerability. 36 millions of websites affected.
From the WordPress 4.8.2 release post: WordPress versions 4.8.1 and earlier are affected by nine security issues:
$wpdb->prepare() can create unexpected and unsafe queries leading to potential SQL injection (SQLi). WordPress core is not directly vulnerable to this issue, but we’ve added hardening to prevent plugins and themes from accidentally causing a vulnerability. Reported by Slavco.
A cross-site scripting (XSS) vulnerability was discovered in the oEmbed discovery. Reported by xknown of the WordPress Security Team.
A cross-site scripting (XSS) vulnerability was discovered in the visual editor. Reported by Rodolfo Assis (@brutelogic) of Sucuri Security.
A path traversal vulnerability was discovered in the file unzipping code. Reported by Alex Chapman (noxrnet).
A cross-site scripting (XSS) vulnerability was discovered in the plugin editor. Reported by 陈瑞琦 (Chen Ruiqi).
An open redirect was discovered on the user and term edit screens. Reported by Yasin Soliman (ysx).
A path traversal vulnerability was discovered in the customizer. Reported by Weston Ruter of the WordPress Security Team.
A cross-site scripting (XSS) vulnerability was discovered in template names. Reported by Luka (sikic).
A cross-site scripting (XSS) vulnerability was discovered in the link modal. Reported by Anas Roubi (qasuar).
In addition to the security issues above, WordPress 4.8.2 contains six maintenance fixes to the 4.8 release series.
Let's do some math.
There are 75 million of WordPress websites. Minimally 36 millions (48%) are affected by 10 vulnerabilities and 75 millions of them are affected by host header attack vulnerability.
More details on:
https://codex.wordpress.org/Version_4.8.2 https://learnwebdevelopment.review/article/wordpress-481-still-vulnerable-to-host-header-attack
I don't understand their math.
Not sure if refuses was used enough.
Really? You're not sure?
You search for CVE-2017-8295. And it is listed as fixed since 4.7.5.
No. "listed as fixed" just means that the exploit site you were looking at didn't update their DB when new versions of WP were released. WordPress.org never listed it as fixed, and no relevant changes were ever made to the WP core code.
When I did a web search for
I found dozens of results, I checked several of them. Every single one shows it as fixed in 4.7.5, I couldn't find a single website to support your claim.
Don't you think that's weird? I think that's pretty weird. Either all of those people got it wrong, or you're a liar. Do you want to guess what my money is on?
If you were not lying, you would have provided proof to support your claim by now, instead of posting more bait comments.
Most of these exploits can only occur with access to the dashboard. So what's the big deal?
A couple things:
Not sure about your math on how many websites use WordPress and are affected. Supposedly there are over 1 billion websites out there, and 26%+ are powered by WordPress. That would be several hundred million sites, not 75 million.
Yes, the exploit is unpatched in 4.8.2, but only sites with poorly configured servers would be affected. This isn't a scientific number, but educated guess, I would say that up 25% of those could fall into that category, not 48% or 100% as you mentioned. (No offense.) But, with more sites using WordPress, the actual number of sites affected could be higher that what you quoted.
Now that still does not mean that the issue should not be fixed, but these are more realistic numbers, yah? (Hey, correct me if I'm wrong on those.) WP still does need to fix it.
Citation required.
Already explained in my other comment: Look at the WP source code.
See: https://www.reddit.com/r/Wordpress/comments/71bvla/36_milions_wordpress_websites_vulnerable_to_9/dnf094y/