Vulnerability Database · Debian · wordpress · Version
wordpress 3.5 dfsg-1
3.5 dfsg-1 is affected by 8 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 0 Medium 0 Low 0 Unrated 8
-
Database updated 23/Oct/2026
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
wordpress 3.5 dfsg-1 vulnerabilities
8 vulnerabilities cover wordpress 3.5 dfsg-1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| WordPress - Open Redirection and Side Request Forgery Vulnerabilities | N/A unrated | 3.6.1+dfsg-1~deb6u9 | 16 Feb 2016 |
| WordPress - Cross-Site Scripting and Privilege Escalation Vulnerabilities | N/A unrated | 3.6.1+dfsg-1~deb6u8 | 30 Sep 2015 |
| WordPress SQL Injection Vulnerability in Debian:6.0 | N/A unrated | 3.6.1+dfsg-1~deb6u7 | 18 Aug 2015 |
| WordPress - Multiple Security Issues | N/A unrated | 3.6.1+dfsg-1~deb6u6 | 01 Jun 2015 |
| WordPress - Denial of Service and Information Disclosure | N/A unrated | 3.6.1+dfsg-1~deb6u5 | 17 Sep 2014 |
| WordPress Security Update - Multiple Vulnerabilities | N/A unrated | 3.6.1+dfsg-1~deb6u2 | 12 Apr 2014 |
| WordPress - Multiple Vulnerabilities | N/A unrated | 3.6.1+dfsg-1~deb6u1 | 14 Sep 2013 |
| WordPress Multiple Vulnerabilities (DSA-2718-1) | N/A unrated | 3.5.2+dfsg-1~deb6u1 | 01 Jul 2013 |
Looking for another version, or everything Vulert holds for wordpress?
Questions
About wordpress 3.5 dfsg-1
Is wordpress 3.5 dfsg-1 vulnerable?
Yes. 8 vulnerabilities in the Vulert database cover wordpress 3.5 dfsg-1: 0 critical, 0 high, 0 medium and 0 low, plus 8 not yet rated. Each entry above names the fixed version to move to.
How do I monitor wordpress for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the wordpress version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.