wp-mail.php in WordPress before 4.7.1 might allow remote attackers to bypass intended posting restrictions via a spoofed mail server with the mail.example.com name.
The product initializes or sets a resource with a default that is intended to be changed by the administrator, but the default is not secure.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Wordpress | Wordpress | * | 4.7 (including) |
| Wordpress | Ubuntu | esm-apps/xenial | * |
| Wordpress | Ubuntu | precise | * |
| Wordpress | Ubuntu | trusty | * |
| Wordpress | Ubuntu | upstream | * |
| Wordpress | Ubuntu | xenial | * |
| Wordpress | Ubuntu | yakkety | * |
Developers often choose default values that leave the product as open and easy to use as possible out-of-the-box, under the assumption that the administrator can (or should) change the default value. However, this ease-of-use comes at a cost when the default is insecure and the administrator does not change it.