What is the severity of CVE-2007-1893?

CVE-2007-1893 is classified as a high severity vulnerability due to its potential to allow unauthorized publishing of posts.

How do I fix CVE-2007-1893?

To fix CVE-2007-1893, it is recommended to upgrade to a later version of WordPress that addresses this vulnerability.

Who is affected by CVE-2007-1893?

CVE-2007-1893 affects remote authenticated users with the contributor role in WordPress versions up to 2.1.2.

What functionality can be exploited in CVE-2007-1893?

CVE-2007-1893 allows contributors to bypass access restrictions and invoke the publish_posts functionality.

Is CVE-2007-1893 still a risk for current WordPress installations?

CVE-2007-1893 is not a risk for current WordPress installations if they have been updated beyond version 2.1.2.

Vulnerability/
CVE-2007-1893

medium

4.9

CWE

264

9/4/2007

7/8/2024

CVE-2007-1893

First published: Mon Apr 09 2007(Updated: )

xmlrpc (xmlrpc.php) in WordPress 2.1.2, and probably earlier, allows remote authenticated users with the contributor role to bypass intended access restrictions and invoke the publish_posts functionality, which can be used to "publish a previously saved post."

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
WordPress	<=2.1.2

Remedy

http://secunia.com/advisories/24751

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2007-1893?
CVE-2007-1893 is classified as a high severity vulnerability due to its potential to allow unauthorized publishing of posts.
How do I fix CVE-2007-1893?
To fix CVE-2007-1893, it is recommended to upgrade to a later version of WordPress that addresses this vulnerability.
Who is affected by CVE-2007-1893?
CVE-2007-1893 affects remote authenticated users with the contributor role in WordPress versions up to 2.1.2.
What functionality can be exploited in CVE-2007-1893?
CVE-2007-1893 allows contributors to bypass access restrictions and invoke the publish_posts functionality.
Is CVE-2007-1893 still a risk for current WordPress installations?
CVE-2007-1893 is not a risk for current WordPress installations if they have been updated beyond version 2.1.2.

agent/type
agent/softwarecombine
agent/remedy
agent/references
agent/weakness
agent/author
agent/severity
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-historical
vendor/wordpress
canonical/wordpress
version/wordpress/2.1.2

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2007-1893?
CVE-2007-1893 is classified as a high severity vulnerability due to its potential to allow unauthorized publishing of posts.
How do I fix CVE-2007-1893?
To fix CVE-2007-1893, it is recommended to upgrade to a later version of WordPress that addresses this vulnerability.
Who is affected by CVE-2007-1893?
CVE-2007-1893 affects remote authenticated users with the contributor role in WordPress versions up to 2.1.2.
What functionality can be exploited in CVE-2007-1893?
CVE-2007-1893 allows contributors to bypass access restrictions and invoke the publish_posts functionality.
Is CVE-2007-1893 still a risk for current WordPress installations?
CVE-2007-1893 is not a risk for current WordPress installations if they have been updated beyond version 2.1.2.