Wordpress contains several cross-site scripting, cross-site request forgery and information leak vulnerabilities.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-apps/wordpress | * | <= 2.1.2 | — |
WordPress is a popular personal publishing platform with a web interface.
WordPress contains cross-site scripting or cross-site scripting forgery vulnerabilities reported by:
Additionally, WordPress prints the full PHP script paths in some error messages.
The cross-site scripting vulnerabilities can be triggered to steal browser session data or cookies. A remote attacker can entice a user to browse to a specially crafted web page that can trigger the cross-site request forgery vulnerability and perform arbitrary WordPress actions with the permissions of the user. Additionally, the path disclosure vulnerability could help an attacker to perform other attacks.
There is no known workaround at this time for all these vulnerabilities.
Due to the numerous recently discovered vulnerabilities in WordPress, this package has been masked in the portage tree. All WordPress users are advised to unmerge it.
# emerge --unmerge "www-apps/wordpress"
WordPress is vulnerable to SQL injection, information disclosure, and cross-site scripting attacks.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-apps/wordpress | * | < 2.0.6 | >= 2.0.6 |
WordPress is a popular personal publishing platform with a web interface.
When decoding trackbacks with alternate character sets, WordPress does not correctly sanitize the entries before further modifying a SQL query. WordPress also displays different error messages in wp-login.php based upon whether or not a user exists. David Kierznowski has discovered that WordPress fails to properly sanitize recent file information in /wp-admin/templates.php before sending that information to a browser.
An attacker could inject arbitrary SQL into WordPress database queries. An attacker could also determine if a WordPress user existed by trying to login as that user, better facilitating brute force attacks. Lastly, an attacker authenticated to view the administrative section of a WordPress instance could try to edit a file with a malicious filename; this may cause arbitrary HTML or JavaScript to be executed in users' browsers viewing /wp-admin/templates.php.
There is no known workaround at this time.
All WordPress users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-apps/wordpress-2.0.6"
Flaws in WordPress allow a Denial of Service, the disclosure of user metadata and the overwriting of restricted files.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-apps/wordpress | * | < 2.0.5 | >= 2.0.5 |
WordPress is a PHP and MySQL based multiuser blogging system.
"random" discovered that users can enter serialized objects as strings in their profiles that will be harmful when unserialized. "adapter" found out that user-edit.php fails to effectively deny non-permitted users access to other user's metadata. Additionally, a directory traversal vulnerability in the wp-db-backup module was discovered.
By entering specially crafted strings in his profile, an attacker can crash PHP or even the web server running WordPress. Additionally, by crafting a simple URL, an attacker can read metadata of any other user, regardless of their own permissions. A user with the permission to use the database backup plugin can possibly overwrite files he otherwise has no access to.
There is no known workaround at this time.
All WordPress users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-apps/wordpress-2.0.5"
A flaw in WordPress allows registered WordPress users to elevate privileges.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-apps/wordpress | * | < 2.0.4 | >= 2.0.4 |
WordPress is a PHP and MySQL based multiuser blogging system.
The WordPress developers have confirmed a vulnerability in capability checking for plugins.
By exploiting a flaw, a user can circumvent WordPress access restrictions when using plugins. The actual impact depends on the configuration of WordPress and may range from trivial to critical, possibly even the execution of arbitrary PHP code.
There is no known workaround at this time.
All WordPress users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-apps/wordpress-2.0.4"
WordPress fails to sufficiently check the format of cached username data.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-apps/wordpress | * | < 2.0.3 | >= 2.0.3 |
WordPress is a PHP and MySQL based content management and publishing system.
rgod discovered that WordPress insufficiently checks the format of cached username data.
An attacker could exploit this vulnerability to execute arbitrary commands by sending a specially crafted username. As of Wordpress 2.0.2 the user data cache is disabled by default.
There are no known workarounds at this time.
All WordPress users should upgrade to the latest available version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-apps/wordpress-2.0.3"
WordPress is vulnerable to an SQL injection vulnerability.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-apps/wordpress | * | <= 1.5.2 | >= 2.0.1 |
WordPress is a PHP and MySQL based content management and publishing system.
Patrik Karlsson reported that WordPress 1.5.2 makes use of an insufficiently filtered User Agent string in SQL queries related to comments posting. This vulnerability was already fixed in the 2.0-series of WordPress.
An attacker could send a comment with a malicious User Agent parameter, resulting in SQL injection and potentially in the subversion of the WordPress database. This vulnerability wouldn't affect WordPress sites which do not allow comments or which require that comments go through a moderator.
Disable or moderate comments on your WordPress blogs.
All WordPress users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-apps/wordpress-2.0.1"
WordPress contains PHP script injection, cross-site scripting and path disclosure vulnerabilities.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-apps/wordpress | * | < 1.5.1.3 | >= 1.5.1.3 |
WordPress is a PHP and MySQL based content management and publishing system.
James Bercegay of the GulfTech Security Research Team discovered that WordPress insufficiently checks data passed to the XML-RPC server. He also discovered that WordPress has several cross-site scripting and full path disclosure vulnerabilities.
An attacker could use the PHP script injection vulnerabilities to execute arbitrary PHP script commands. Furthermore the cross-site scripting vulnerabilities could be exploited to execute arbitrary script code in a user's browser session in context of a vulnerable site.
There are no known workarounds at this time.
All WordPress users should upgrade to the latest available version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-apps/wordpress-1.5.1.3"
Wordpress contains SQL injection and XSS vulnerabilities.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-apps/wordpress | * | < 1.5.1.2 | >= 1.5.1.2 |
WordPress is a PHP and MySQL based content management and publishing system.
Due to a lack of input validation, WordPress is vulnerable to SQL injection and XSS attacks.
An attacker could use the SQL injection vulnerabilities to gain information from the database. Furthermore the cross-site scripting issues give an attacker the ability to inject and execute malicious script code or to steal cookie-based authentication credentials, potentially compromising the victim's browser.
There is no known workaround at this time.
All Wordpress users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-apps/wordpress-1.5.1.2"
WordPress contains HTTP response splitting and cross-site scripting vulnerabilities.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-apps/wordpress | * | < 1.2.2 | >= 1.2.2 |
WordPress is a PHP and MySQL based content management and publishing system.
Due to the lack of input validation in the administration panel scripts, WordPress is vulnerable to HTTP response splitting and cross-site scripting attacks.
A malicious user could inject arbitrary response data, leading to content spoofing, web cache poisoning and other cross-site scripting or HTTP response splitting attacks. This could result in compromising the victim's data or browser.
There is no known workaround at this time.
All WordPress users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-apps/wordpress-1.2.2"