WordPress - Multiple XSS and Information Disclosure Vulnerabilities

wordpress Updated 02 Oct 2025

Summary

11/03/2011
N/A
Yes i
Unrated
Not published

DSA-2190-1: wordpress - several. Affects wordpress versions < 3.0.5+dfsg-0+squeeze1. Fixed in 3.0.5+dfsg-0+squeeze1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

WordPress is a popular weblog manager used for creating and managing websites. It provides a user-friendly interface for content creation and customization. The package 'wordpress' in Debian version 6.0 (lenny) is affected by multiple vulnerabilities, including two Cross-Site Scripting (XSS) bugs and one potential information disclosure issue.

Vulnerability Detail

The first vulnerability, identified as CVE-2011-0700, occurs when input passed via the post title during Quick Edit or Bulk Edit actions, and via the post_status, comment_status, and ping_status parameters, is not properly sanitized. This can lead to the execution of malicious scripts or unauthorized disclosure of sensitive information. Additionally, certain input passed via tags in the tags meta-box is also not properly sanitized, posing a similar risk.

The second vulnerability, CVE-2011-0701, involves WordPress incorrectly enforcing user access restrictions when accessing posts through the media uploader. This can be exploited to disclose the contents of private or draft posts, potentially exposing sensitive information.

How To Fix

Minimum fixed version

3.0.5+dfsg-0+squeeze1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade wordpress

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There are no specific workarounds mentioned for these vulnerabilities.

Conclusion

WordPress users are advised to upgrade their 'wordpress' packages to the fixed versions mentioned above to address these vulnerabilities. Promptly applying security updates is crucial to maintain the security and integrity of WordPress installations. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for wordpress →

Share this vulnerability

FAQ

These vulnerabilities can allow an attacker to execute malicious scripts, potentially compromising the security of the affected WordPress installation. They can also lead to the unauthorized disclosure of sensitive information, such as private or draft posts.

No, only the 'wordpress' package in Debian version 6.0 (lenny) is affected. The vulnerabilities have been fixed in later versions.

There is no specific information provided about known exploits for these vulnerabilities. However, it is always recommended to apply security updates promptly to mitigate the risk of exploitation.

Yes, these vulnerabilities can be exploited remotely if an attacker can access the affected WordPress installation and send malicious input to the vulnerable components.

There is no specific information provided about active exploitation of these vulnerabilities. However, it is advisable to stay updated with security patches and monitor for any suspicious activity.

Related vulnerabilities

Recent vulnerabilities recorded for wordpress.

How To Fix

Minimum fixed version

3.0.5+dfsg-0+squeeze1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade wordpress

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback