ID CVE-2015-2213
Summary SQL injection vulnerability in the wp_untrash_post_comments function in wp-includes/post.php in WordPress before 4.2.4 allows remote attackers to execute arbitrary SQL commands via a comment that is mishandled after retrieval from the trash.
References
Vulnerable Configurations
  • WordPress 4.2.3
    cpe:2.3:a:wordpress:wordpress:4.2.3
CVSS
Base: 7.5 (as of 09-11-2015 - 11:16)
Impact:
Exploitability:
CWE CWE-89
CAPEC
  • Command Line Execution through SQL Injection
    An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new commands to be executed on the host.
  • Object Relational Mapping Injection
    An attacker leverages a weakness present in the database access layer code generated with an Object Relational Mapping (ORM) tool or a weakness in the way that a developer used a persistence framework to inject his or her own SQL commands to be executed against the underlying database. The attack here is similar to plain SQL injection, except that the application does not use JDBC to directly talk to the database, but instead it uses a data access layer generated by an ORM tool or framework (e.g. Hibernate). While most of the time code generated by an ORM tool contains safe access methods that are immune to SQL injection, sometimes either due to some weakness in the generated code or due to the fact that the developer failed to use the generated access methods properly, SQL injection is still possible.
  • SQL Injection through SOAP Parameter Tampering
    An attacker modifies the parameters of the SOAP message that is sent from the service consumer to the service provider to initiate a SQL injection attack. On the service provider side, the SOAP message is parsed and parameters are not properly validated before being used to access a database in a way that does not use parameter binding, thus enabling the attacker to control the structure of the executed SQL query. This pattern describes a SQL injection attack with the delivery mechanism being a SOAP message.
  • Expanding Control over the Operating System from the Database
    An attacker is able to leverage access gained to the database to read / write data to the file system, compromise the operating system, create a tunnel for accessing the host machine, and use this access to potentially attack other machines on the same network as the database machine. Traditionally SQL injections attacks are viewed as a way to gain unauthorized read access to the data stored in the database, modify the data in the database, delete the data, etc. However, almost every data base management system (DBMS) system includes facilities that if compromised allow an attacker complete access to the file system, operating system, and full access to the host running the database. The attacker can then use this privileged access to launch subsequent attacks. These facilities include dropping into a command shell, creating user defined functions that can call system level libraries present on the host machine, stored procedures, etc.
  • SQL Injection
    This attack exploits target software that constructs SQL statements based on user input. An attacker crafts input strings so that when the target software constructs SQL statements based on the input, the resulting SQL statement performs actions other than those the application intended. SQL Injection results from failure of the application to appropriately validate input. When specially crafted user-controlled input consisting of SQL syntax is used without proper validation as part of SQL queries, it is possible to glean information from the database in ways not envisaged during application design. Depending upon the database and the design of the application, it may also be possible to leverage injection to have the database execute system-related commands of the attackers' choice. SQL Injection enables an attacker to talk directly to the database, thus bypassing the application completely. Successful injection can cause information disclosure as well as ability to add or modify data in the database. In order to successfully inject SQL and retrieve information from a database, an attacker:
  • Blind SQL Injection
    Blind SQL Injection results from an insufficient mitigation for SQL Injection. Although suppressing database error messages are considered best practice, the suppression alone is not sufficient to prevent SQL Injection. Blind SQL Injection is a form of SQL Injection that overcomes the lack of error messages. Without the error messages that facilitate SQL Injection, the attacker constructs input strings that probe the target through simple Boolean SQL expressions. The attacker can determine if the syntax and structure of the injection was successful based on whether the query was executed or not. Applied iteratively, the attacker determines how and where the target is vulnerable to SQL Injection. For example, an attacker may try entering something like "username' AND 1=1; --" in an input field. If the result is the same as when the attacker entered "username" in the field, then the attacker knows that the application is vulnerable to SQL Injection. The attacker can then ask yes/no questions from the database server to extract information from it. For example, the attacker can extract table names from a database using the following types of queries: If the above query executes properly, then the attacker knows that the first character in a table name in the database is a letter between m and z. If it doesn't, then the attacker knows that the character must be between a and l (assuming of course that table names only contain alphabetic characters). By performing a binary search on all character positions, the attacker can determine all table names in the database. Subsequently, the attacker may execute an actual attack and send something like:
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL PARTIAL
nessus via4
  • NASL family CGI abuses
    NASL id WORDPRESS_4_2_4.NASL
    description According to its version number, the WordPress application running on the remote web server is prior to 4.2.4. It is, therefore, potentially affected by multiple vulnerabilities : - A SQL injection vulnerability exists in the post.php script due to a failure to sanitize user-supplied input to the 'comment_ID' parameter before using it in SQL queries. A remote attacker can exploit this to inject SQL queries against the back-end database, allowing the disclosure or manipulation of data. (CVE-2015-2213) - The class-wp-customize-widgets.php script contains an unspecified flaw that allows an attacker to perform a side-channel timing attack. No other details are available. (CVE-2015-5730) - A cross-site scripting vulnerability exists due to the default-widgets.php script not validating input to widget titles before returning it to users. A remote attacker, using a crafted request, can exploit this to execute arbitrary script in the user's browser session. (CVE-2015-5732) - A cross-site scripting vulnerability exists due to the nav-menu.js script not validating input to accessibility helper titles before returning it to users. A remote attacker, using a crafted request, can exploit this to execute arbitrary script in the user's browser session. (CVE-2015-5733) - A cross-site scripting vulnerability exists due to the theme.php script not validating input before returning it to users. A remote attacker, using a crafted request, can exploit this to execute arbitrary script in the user's browser session. (CVE-2015-5734) Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.
    last seen 2019-02-21
    modified 2018-08-07
    plugin id 85243
    published 2015-08-05
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=85243
    title WordPress < 4.2.4 Multiple Vulnerabilities
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-3332.NASL
    description Several vulnerabilities have been fixed in Wordpress, the popular blogging engine. - CVE-2015-2213 SQL Injection allowed a remote attacker to compromise the site. - CVE-2015-5622 The robustness of the shortcodes HTML tags filter has been improved. The parsing is a bit more strict, which may affect your installation. This is the corrected version of the patch that needed to be reverted in DSA 3328-2. - CVE-2015-5730 A potential timing side-channel attack in widgets. - CVE-2015-5731 An attacker could lock a post that was being edited. - CVE-2015-5732 Cross site scripting in a widget title allows an attacker to steal sensitive information. - CVE-2015-5734 Fix some broken links in the legacy theme preview. The issues were discovered by Marc-Alexandre Montpas of Sucuri, Helen Hou-Sandi of the WordPress security team, Netanel Rubin of Check Point, Ivan Grigorov, Johannes Schmitt of Scrutinizer and Mohamed A. Baset.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 85355
    published 2015-08-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=85355
    title Debian DSA-3332-1 : wordpress - security update
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DLA-294.NASL
    description Several vulnerabilities have been fixed in Wordpress, the popular blogging engine. CVE-2015-2213 SQL Injection allowed a remote attacker to compromise the site. CVE-2015-5622 The robustness of the shortcodes HTML tags filter has been improved. The parsing is a bit more strict, which may affect your installation. This is the corrected version of the patch that needed to be reverted in DSA 3328-2. CVE-2015-5731 An attacker could lock a post that was being edited. CVE-2015-5732 Cross site scripting in a widget title allows an attacker to steal sensitive information. CVE-2015-5734 Fix some broken links in the legacy theme preview. The issues were discovered by Marc-Alexandre Montpas of Sucuri, Helen Hou-Sandí of the WordPress security team, Netanel Rubin of Check Point, Ivan Grigorov, Johannes Schmitt of Scrutinizer and Mohamed A. Baset. We recommend that you upgrade your wordpress packages. NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-07-06
    plugin id 85546
    published 2015-08-20
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=85546
    title Debian DLA-294-1 : wordpress security update
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2015-12750.NASL
    description **WordPress 4.2.4 Security and Maintenance Release** WordPress 4.2.4 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately. This release addresses six issues, including three cross-site scripting vulnerabilities and a potential SQL injection that could be used to compromise a site, which were discovered by Marc-Alexandre Montpas of Sucuri, Helen Hou-Sandi of the WordPress security team, Netanel Rubin of Check Point, and Ivan Grigorov. It also includes a fix for a potential timing side-channel attack, discovered by Johannes Schmitt of Scrutinizer, and prevents an attacker from locking a post from being edited, discovered by Mohamed A. Baset. Our thanks to those who have practiced responsible disclosure of security issues. WordPress 4.2.4 also fixes four bugs. For more information, see: the release notes or consult the list of changes. - the release notes: https://codex.wordpress.org/Version_4.2.4 - the list of changes: https://core.trac.wordpress.org/log/branches/4.2?rev=3 3573&stop_rev=33396 Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2015-11-10
    plugin id 85317
    published 2015-08-11
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=85317
    title Fedora 23 : wordpress-4.2.4-1.fc23 (2015-12750)
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_AC5EC8E33C6C11E5B92100A0986F28C4.NASL
    description Gary Pendergast reports : WordPress 4.2.4 fixes three cross-site scripting vulnerabilities and a potential SQL injection that could be used to compromise a site.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 85258
    published 2015-08-07
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=85258
    title FreeBSD : wordpress -- Multiple vulnerability (ac5ec8e3-3c6c-11e5-b921-00a0986f28c4)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2015-12148.NASL
    description **WordPress 4.2.4 Security and Maintenance Release** WordPress 4.2.4 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately. This release addresses six issues, including three cross-site scripting vulnerabilities and a potential SQL injection that could be used to compromise a site, which were discovered by Marc-Alexandre Montpas of Sucuri, Helen Hou-Sandi of the WordPress security team, Netanel Rubin of Check Point, and Ivan Grigorov. It also includes a fix for a potential timing side-channel attack, discovered by Johannes Schmitt of Scrutinizer, and prevents an attacker from locking a post from being edited, discovered by Mohamed A. Baset. Our thanks to those who have practiced responsible disclosure of security issues. WordPress 4.2.4 also fixes four bugs. For more information, see: the release notes or consult the list of changes. - the release notes: https://codex.wordpress.org/Version_4.2.4 - the list of changes: https://core.trac.wordpress.org/log/branches/4.2?rev=3 3573&stop_rev=33396 **WordPress 4.2.3 Security and Maintenance Release** WordPress 4.2.3 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately. WordPress versions 4.2.2 and earlier are affected by a cross-site scripting vulnerability, which could allow users with the Contributor or Author role to compromise a site. This was initially reported by Jon Cave and fixed by Robert Chapin, both of the WordPress security team, and later reported by Jouko Pynnonen. We also fixed an issue where it was possible for a user with Subscriber permissions to create a draft through Quick Draft. Reported by Netanel Rubin from Check Point Software Technologies. Our thanks to those who have practiced responsible disclosure of security issues. WordPress 4.2.3 also contains fixes for 20 bugs from 4.2. For more information, see : - the release notes: https://codex.wordpress.org/Version_4.2.3 - the list of changes: https://core.trac.wordpress.org/log/branches/4.2?rev=3 3382&stop_rev=32430 Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2015-11-10
    plugin id 85389
    published 2015-08-14
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=85389
    title Fedora 21 : wordpress-4.2.4-1.fc21 (2015-12148)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2015-12235.NASL
    description **WordPress 4.2.4 Security and Maintenance Release** WordPress 4.2.4 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately. This release addresses six issues, including three cross-site scripting vulnerabilities and a potential SQL injection that could be used to compromise a site, which were discovered by Marc-Alexandre Montpas of Sucuri, Helen Hou-Sandi of the WordPress security team, Netanel Rubin of Check Point, and Ivan Grigorov. It also includes a fix for a potential timing side-channel attack, discovered by Johannes Schmitt of Scrutinizer, and prevents an attacker from locking a post from being edited, discovered by Mohamed A. Baset. Our thanks to those who have practiced responsible disclosure of security issues. WordPress 4.2.4 also fixes four bugs. For more information, see: the release notes or consult the list of changes. - the release notes: https://codex.wordpress.org/Version_4.2.4 - the list of changes: https://core.trac.wordpress.org/log/branches/4.2?rev=3 3573&stop_rev=33396 **WordPress 4.2.3 Security and Maintenance Release** WordPress 4.2.3 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately. WordPress versions 4.2.2 and earlier are affected by a cross-site scripting vulnerability, which could allow users with the Contributor or Author role to compromise a site. This was initially reported by Jon Cave and fixed by Robert Chapin, both of the WordPress security team, and later reported by Jouko Pynnonen. We also fixed an issue where it was possible for a user with Subscriber permissions to create a draft through Quick Draft. Reported by Netanel Rubin from Check Point Software Technologies. Our thanks to those who have practiced responsible disclosure of security issues. WordPress 4.2.3 also contains fixes for 20 bugs from 4.2. For more information, see : - the release notes: https://codex.wordpress.org/Version_4.2.3 - the list of changes: https://core.trac.wordpress.org/log/branches/4.2?rev=3 3382&stop_rev=32430 Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2015-11-10
    plugin id 85390
    published 2015-08-14
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=85390
    title Fedora 22 : wordpress-4.2.4-1.fc22 (2015-12235)
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-3383.NASL
    description Several vulnerabilities were discovered in Wordpress, a web blogging tool. The Common Vulnerabilities and Exposures project identifies the following problems : - CVE-2015-2213 SQL Injection allowed a remote attacker to compromise the site. - CVE-2015-5622 The robustness of the shortcodes HTML tags filter has been improved. The parsing is a bit more strict, which may affect your installation. - CVE-2015-5714 A cross-site scripting vulnerability when processing shortcode tags. - CVE-2015-5715 A vulnerability has been discovered, allowing users without proper permissions to publish private posts and make them sticky. - CVE-2015-5731 An attacker could lock a post that was being edited. - CVE-2015-5732 Cross-site scripting in a widget title allows an attacker to steal sensitive information. - CVE-2015-5734 Fix some broken links in the legacy theme preview. - CVE-2015-7989 A cross-site scripting vulnerability in user list tables.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 86666
    published 2015-10-30
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=86666
    title Debian DSA-3383-1 : wordpress - security update
refmap via4
bid 76160
confirm
debian
  • DSA-3332
  • DSA-3383
misc https://wpvulndb.com/vulnerabilities/8126
mlist [oss-security] 20150804 Re: CVE request: WordPress 4.2.3 and earlier multiple vulnerabilities
sectrack 1033178
Last major update 07-12-2016 - 13:10
Published 09-11-2015 - 06:59
Last modified 03-11-2017 - 21:29
Back to Top