What is the severity of CVE-2007-0539?

CVE-2007-0539 is classified as a denial of service vulnerability.

How do I fix CVE-2007-0539?

To fix CVE-2007-0539, upgrade your WordPress installation to version 2.1 or later.

What is the impact of CVE-2007-0539?

The impact of CVE-2007-0539 can result in excessive bandwidth or thread consumption, leading to potential service outages.

Which versions of WordPress are affected by CVE-2007-0539?

WordPress versions prior to 2.1 are affected by CVE-2007-0539.

What is the primary vulnerability type of CVE-2007-0539?

The primary vulnerability type of CVE-2007-0539 is the denial of service through uncontrolled download sessions.

Vulnerability/
CVE-2007-0539

high

7.8

CWE

NVD-CWE-Other

29/1/2007

7/8/2024

CVE-2007-0539

First published: Mon Jan 29 2007(Updated: )

The wp_remote_fopen function in WordPress before 2.1 allows remote attackers to cause a denial of service (bandwidth or thread consumption) via pingback service calls with a source URI that corresponds to a large file, which triggers a long download session without a timeout constraint.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
WordPress	<=2.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2007-0539?
CVE-2007-0539 is classified as a denial of service vulnerability.
How do I fix CVE-2007-0539?
To fix CVE-2007-0539, upgrade your WordPress installation to version 2.1 or later.
What is the impact of CVE-2007-0539?
The impact of CVE-2007-0539 can result in excessive bandwidth or thread consumption, leading to potential service outages.
Which versions of WordPress are affected by CVE-2007-0539?
WordPress versions prior to 2.1 are affected by CVE-2007-0539.
What is the primary vulnerability type of CVE-2007-0539?
The primary vulnerability type of CVE-2007-0539 is the denial of service through uncontrolled download sessions.

agent/type
agent/softwarecombine
agent/author
agent/references
agent/severity
agent/weakness
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.0

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-0539?
CVE-2007-0539 is classified as a denial of service vulnerability.
How do I fix CVE-2007-0539?
To fix CVE-2007-0539, upgrade your WordPress installation to version 2.1 or later.
What is the impact of CVE-2007-0539?
The impact of CVE-2007-0539 can result in excessive bandwidth or thread consumption, leading to potential service outages.
Which versions of WordPress are affected by CVE-2007-0539?
WordPress versions prior to 2.1 are affected by CVE-2007-0539.
What is the primary vulnerability type of CVE-2007-0539?
The primary vulnerability type of CVE-2007-0539 is the denial of service through uncontrolled download sessions.