Critical WordPress REST API Bug: Prevent Your Blog From Being Hacked!

Description

Last week, WordPress patched three security flaws, but just yesterday the company disclosed about a nasty then-secret zero-day vulnerability that let remote unauthorized hackers modify the content of any post or page within a WordPress site.

The nasty bug resides in Wordpress REST API that would lead to the creation of two new vulnerabilities: Remote privilege escalation and Content injection bugs.

Wordpress is the world's most popular content management system (CMS) used on millions of websites. The CMS recently added and enabled REST API by default on WordPress 4.7.0.

Flaw lets Unauthorised Hacker Redirect Visitors to Malicious Exploits

The vulnerability is easy to exploit and affects versions 4.7 and 4.7.1 of the Wordpress content management system (CMS), allowing an unauthenticated attacker to modify all pages on unpatched sites and redirect visitors to malicious exploits and a large number of attacks.

The vulnerability was discovered and reported by Marc-Alexandre Montpas from Sucuri to the WordPress security team who handled the matter very well by releasing a patch, but not disclosing details about the flaw in an effort to keep hackers away from exploiting the bug before millions of websites implement the patch.

> "This privilege escalation vulnerability affects the WordPress REST API," Montpas writes in a blog post. "One of these REST endpoints allows access (via the API) to view, edit, delete and create posts. Within this particular endpoint, a subtle bug allows visitors to edit any post on the site."

Why WordPress Delayed the Vulnerability Disclosure

The issue was discovered on January 22nd, patched on January 26th and the fix was made available in release 4.7.2 to websites using the popular CMS.

Sucuri security providers and hosts worked closely with Wordpress security team for over a week to install the patch, ensuring that the issue was dealt with in short order before it became public.

The company also tipped off security companies including SiteLock, Cloudflare, and Incapsula over 9 days between disclosure and patch.

> "We believe transparency is in the public's best interest...[and]... in this case, we intentionally delayed disclosing the issue by one week to ensure the safety of millions of additional WordPress sites."

> "Data from all four WAFs and WordPress hosts showed no indication that the vulnerability had been exploited in the wild. As a result, we made the decision to delay disclosure of this particular issue to give time for automatic updates to run and ensure as many users as possible were protected before the issue was made public."

Patch your CMS Now!

The flaw has been rated critical, although the fix has automatically been deployed on millions of WordPress installations in the few hours after the patch was issued.

For a more technical explanation about the vulnerability, you can head on the Sucuri's official blog post.

WordPress admins who have not yet implemented the patch against the nasty vulnerability are strongly advised to update their CMS to Wordpress version 4.7.2.

All product names, logos, and brands are property of their respective owners. All company, product and service names used in this website are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.If you are an owner of some content and want it to be removed, please mail to content@vulners.com Vulners, 2018

Protected by

{"id": "THN:E4010340D23CA7165FD477AC7534F7DB", "type": "thn", "bulletinFamily": "info", "title": "Critical WordPress REST API Bug: Prevent Your Blog From Being Hacked!", "description": "[![wordpress-exploit-hack](https://3.bp.blogspot.com/-TGa5NTcXv-Q/WJLW0XrgBmI/AAAAAAAArSA/cg2VorAAKeEWSpmUHxoUkU7K9U6KvU8mACLcB/s1600/wordpress-exploit-hack.png)](<https://3.bp.blogspot.com/-TGa5NTcXv-Q/WJLW0XrgBmI/AAAAAAAArSA/cg2VorAAKeEWSpmUHxoUkU7K9U6KvU8mACLcB/s1600/wordpress-exploit-hack.png>)\n\nLast week, WordPress patched three security flaws, but just yesterday the company disclosed about a nasty then-secret zero-day vulnerability that let remote unauthorized hackers modify the content of any post or page within a WordPress site. \n \nThe nasty bug resides in Wordpress REST API that would lead to the creation of two new vulnerabilities: Remote privilege escalation and Content injection bugs. \n \nWordpress is the world's most popular content management system (CMS) used on millions of websites. The CMS recently added and enabled REST API by default on WordPress 4.7.0. \n \n\n\n### Flaw lets Unauthorised Hacker Redirect Visitors to Malicious Exploits\n\n \nThe vulnerability is easy to exploit and affects versions 4.7 and 4.7.1 of the Wordpress content management system (CMS), allowing an unauthenticated attacker to modify all pages on unpatched sites and redirect visitors to malicious exploits and a large number of attacks. \n \nThe vulnerability was discovered and reported by Marc-Alexandre Montpas from Sucuri to the WordPress security team who handled the matter very well by releasing a patch, but not disclosing details about the flaw in an effort to keep hackers away from exploiting the bug before millions of websites implement the patch. \n\n\n> \"This privilege escalation vulnerability affects the WordPress REST API,\" Montpas writes in a [blog post](<https://blog.sucuri.net/2017/02/content-injection-vulnerability-wordpress-rest-api.html>). \"One of these REST endpoints allows access (via the API) to view, edit, delete and create posts. Within this particular endpoint, a subtle bug allows visitors to edit any post on the site.\"\n\n \n\n\n### Why WordPress Delayed the Vulnerability Disclosure\n\n \nThe issue was discovered on January 22nd, patched on January 26th and the fix was made available in [release 4.7.2](<https://wordpress.org/news/2017/01/wordpress-4-7-2-security-release/>) to websites using the popular CMS. \n \nSucuri security providers and hosts worked closely with Wordpress security team for over a week to install the patch, ensuring that the issue was dealt with in short order before it became public. \n \nThe company also tipped off security companies including SiteLock, Cloudflare, and Incapsula over 9 days between disclosure and patch. \n \nHere's what the Wordpress core contributor Aaron Campbell says about the delay in the [vulnerability disclosure](<https://make.wordpress.org/core/2017/02/01/disclosure-of-additional-security-fix-in-wordpress-4-7-2/>): \n\n\n> \"We believe transparency is in the public's best interest...[and]... in this case, we intentionally delayed disclosing the issue by one week to ensure the safety of millions of additional WordPress sites.\" \n\n> \"Data from all four WAFs and WordPress hosts showed no indication that the vulnerability had been exploited in the wild. As a result, we made the decision to delay disclosure of this particular issue to give time for automatic updates to run and ensure as many users as possible were protected before the issue was made public.\"\n\n \n\n\n### Patch your CMS Now!\n\n \nThe flaw has been rated critical, although the fix has automatically been deployed on millions of WordPress installations in the few hours after the patch was issued. \n \nFor a more technical explanation about the vulnerability, you can head on the Sucuri's [official blog post](<https://blog.sucuri.net/2017/02/content-injection-vulnerability-wordpress-rest-api.html>). \n \nWordPress admins who have not yet implemented the patch against the nasty vulnerability are strongly advised to update their CMS to Wordpress version 4.7.2.\n", "published": "2017-02-01T21:24:00", "modified": "2017-02-02T08:24:11", "cvss": {"score": 0.0, "vector": "NONE"}, "href": "https://thehackernews.com/2017/02/wordpress-exploit-patch.html", "reporter": "Swati Khandelwal", "references": [], "cvelist": [], "lastseen": "2018-01-27T10:06:59", "history": [], "viewCount": 0, "enchantments": {"score": {"vector": "NONE", "value": 6.8}, "vulnersScore": 6.8}, "objectVersion": "1.4", "_object_type": "robots.models.thn.ThnBulletin", "_object_types": ["robots.models.thn.ThnBulletin", "robots.models.base.Bulletin"]}