Search for packages
| purl | pkg:deb/debian/wordpress@5.7.11%2Bdfsg1-0%2Bdeb11u1 |
| Next non-vulnerable version | 6.8.3+dfsg1-0+deb13u1 |
| Latest non-vulnerable version | 6.8.3+dfsg1-0+deb13u1 |
| Risk | 3.4 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-4g2n-5v12-yuff
Aliases: CVE-2024-31111 |
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Automattic WordPress allows Stored XSS.This issue affects WordPress: from 6.5 through 6.5.4, from 6.4 through 6.4.4, from 6.3 through 6.3.4, from 6.2 through 6.2.5, from 6.1 through 6.1.6, from 6.0 through 6.0.8, from 5.9 through 5.9.9. |
Affected by 2 other vulnerabilities. |
|
VCID-532z-9qbb-dyfw
Aliases: CVE-2025-58246 |
Insertion of Sensitive Information Into Sent Data vulnerability in WordPress allows Retrieve Embedded Sensitive Data. The WordPress Core security team is aware of the issue and is already working on a fix. This is a low-severity vulnerability. Contributor-level privileges required in order to exploit it. This issue affects WordPress: from 6.8 through 6.8.2, from 6.7 through 6.7.3, from 6.6 through 6.6.3, from 6.5 through 6.5.6, from 6.4 through 6.4.6, from 6.3 through 6.3.6, from 6.2 through 6.2.7, from 6.1 through 6.1.8, from 6.0 through 6.0.10, from 5.9 through 5.9.11, from 5.8 through 5.8.11, from 5.7 through 5.7.13, from 5.6 through 5.6.15, from 5.5 through 5.5.16, from 5.4 through 5.4.17, from 5.3 through 5.3.19, from 5.2 through 5.2.22, from 5.1 through 5.1.20, from 5.0 through 5.0.23, from 4.9 through 4.9.27, from 4.8 through 4.8.26, from 4.7 through 4.7.30. |
Affected by 2 other vulnerabilities. |
|
VCID-gyaq-8pvh-p7gg
Aliases: CVE-2012-6707 |
WordPress through 4.8.2 uses a weak MD5-based password hashing algorithm, which makes it easier for attackers to determine cleartext values by leveraging access to the hash values. NOTE: the approach to changing this may not be fully compatible with certain use cases, such as migration of a WordPress site from a web host that uses a recent PHP version to a different web host that uses PHP 5.2. These use cases are plausible (but very unlikely) based on statistics showing widespread deployment of WordPress with obsolete PHP versions. |
Affected by 0 other vulnerabilities. |
|
VCID-jghn-eujf-zbdn
Aliases: CVE-2023-5692 |
WordPress Core is vulnerable to Sensitive Information Exposure in versions up to, and including, 6.4.3 via the redirect_guess_404_permalink function. This can allow unauthenticated attackers to expose the slug of a custom post whose 'publicly_queryable' post status has been set to 'false'. |
Affected by 0 other vulnerabilities. |
|
VCID-m8mf-t2td-67h7
Aliases: CVE-2024-6307 |
WordPress Core is vulnerable to Stored Cross-Site Scripting via the HTML API in various versions prior to 6.5.5 due to insufficient input sanitization and output escaping on URLs. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. |
Affected by 2 other vulnerabilities. |
|
VCID-yqam-kpce-dfg7
Aliases: CVE-2021-44223 |
WordPress before 5.8 lacks support for the Update URI plugin header. This makes it easier for remote attackers to execute arbitrary code via a supply-chain attack against WordPress installations that use any plugin for which the slug satisfies the naming constraints of the WordPress.org Plugin Directory but is not yet present in that directory. |
Affected by 2 other vulnerabilities. |
|
VCID-zj9a-shru-e7gs
Aliases: CVE-2025-58674 |
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WordPress allows Stored XSS. WordPress core security team is aware of the issue and working on a fix. This is low severity vulnerability that requires an attacker to have Author or higher user privileges to execute the attack vector.This issue affects WordPress: from 6.8 through 6.8.2, from 6.7 through 6.7.3, from 6.6 through 6.6.3, from 6.5 through 6.5.6, from 6.4 through 6.4.6, from 6.3 through 6.3.6, from 6.2 through 6.2.7, from 6.1 through 6.1.8, from 6.0 through 6.0.10, from 5.9 through 5.9.11, from 5.8 through 5.8.11, from 5.7 through 5.7.13, from 5.6 through 5.6.15, from 5.5 through 5.5.16, from 5.4 through 5.4.17, from 5.3 through 5.3.19, from 5.2 through 5.2.22, from 5.1 through 5.1.20, from 5.0 through 5.0.23, from 4.9 through 4.9.27, from 4.8 through 4.8.26, from 4.7 through 4.7.30. |
Affected by 2 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-1by8-54pr-ubcw | In affected versions of WordPress, users with low privileges (like contributors and authors) can use the embed block in a certain way to inject unfiltered HTML in the block editor. When affected posts are viewed by a higher privileged user, this could lead to script execution in the editor/wp-admin. This has been patched in version 5.4.2, along with all the previously affected versions via a minor release (5.3.4, 5.2.7, 5.1.6, 5.0.10, 4.9.15, 4.8.14, 4.7.18, 4.6.19, 4.5.22, 4.4.23, 4.3.24, 4.2.28, 4.1.31, 4.0.31, 3.9.32, 3.8.34, 3.7.34). |
CVE-2020-4046
|
| VCID-1j31-f88g-kfe7 | security update |
CVE-2021-29450
|
| VCID-1tw6-axgs-f3hy | security update |
CVE-2020-11027
|
| VCID-2gqt-ngbw-xyby | security update |
CVE-2022-21664
|
| VCID-2jgs-b7r7-zygv | In affected versions of WordPress, a special payload can be crafted that can lead to scripts getting executed within the search block of the block editor. This requires an authenticated user with the ability to add content. This has been patched in version 5.4.1, along with all the previously affected versions via a minor release (5.3.3, 5.2.6, 5.1.5, 5.0.9, 4.9.14, 4.8.13, 4.7.17, 4.6.18, 4.5.21, 4.4.22, 4.3.23, 4.2.27, 4.1.30, 4.0.30, 3.9.31, 3.8.33, 3.7.33). |
CVE-2020-11030
|
| VCID-3171-8hu9-4uev | security update |
CVE-2019-17675
|
| VCID-3572-tc84-pyhv | security update |
CVE-2023-2745
|
| VCID-3veg-k8v2-tyhr | security update |
CVE-2019-17671
|
| VCID-47fm-x1rg-vbct | security update |
CVE-2024-31210
|
| VCID-47he-853j-8qdn | WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. In affected versions output data of the function wp_die() can be leaked under certain conditions, which can include data like nonces. It can then be used to perform actions on your behalf. This has been patched in WordPress 5.8.1, along with any older affected versions via minor releases. It's strongly recommended that you keep auto-updates enabled to receive the fix. |
CVE-2021-39200
|
| VCID-4ty5-fp9a-8qhg | security update |
CVE-2019-16781
|
| VCID-5698-c229-bqc9 | WordPress before 5.2.4 has a Server Side Request Forgery (SSRF) vulnerability because Windows paths are mishandled during certain validation of relative URLs. |
CVE-2019-17670
|
| VCID-6j54-w242-hfce | security update |
CVE-2022-43504
|
| VCID-722f-e2hf-xyc9 | security update |
CVE-2023-5561
|
| VCID-767p-btpd-tudb | security update |
CVE-2019-17669
|
| VCID-8mat-2mjd-7fgm | WordPress before 5.1.1 does not properly filter comment content, leading to Remote Code Execution by unauthenticated users in a default configuration. This occurs because CSRF protection is mishandled, and because Search Engine Optimization of A elements is performed incorrectly, leading to XSS. The XSS results in administrative access, which allows arbitrary changes to .php files. This is related to wp-admin/includes/ajax-actions.php and wp-includes/comment.php. |
CVE-2019-9787
|
| VCID-92fa-nrxb-e3gj | security update |
CVE-2020-28032
|
| VCID-98e3-ffna-jfbs | security update |
CVE-2019-17674
|
| VCID-agpu-husf-6be4 | security update |
CVE-2019-16217
|
| VCID-ajrt-bhrw-k7an | security update |
CVE-2019-16220
|
| VCID-aup2-49ee-jkdf | security update |
CVE-2019-16222
|
| VCID-azsx-2ydf-zyag | security update |
CVE-2020-4050
|
| VCID-azyj-28v6-ufhg | security update |
CVE-2021-39201
|
| VCID-bb3n-jh6p-vfhm | security update |
CVE-2022-21661
|
| VCID-c2ta-7w7f-kbed | security update |
CVE-2019-16218
|
| VCID-dzgs-vwe3-fub1 | security update |
CVE-2019-20042
|
| VCID-e8zy-mzdn-g7gz | security update |
DSA-5279-2 wordpress
|
| VCID-ejtq-a5ca-ffbu | security update |
CVE-2019-16221
|
| VCID-fpwa-74w6-mugt | security update |
CVE-2019-16780
|
| VCID-fra3-hye6-kqh7 | Insecure Deserialization of untrusted data in rmccue/requests ### Impact Unserialization of untrusted data. ### Patches The issue has been patched and users of `Requests` 1.6.0, 1.6.1 and 1.7.0 should update to version 1.8.0. ### References Publications about the vulnerability: * https://dannewitz.ninja/posts/php-unserialize-object-injection-yet-another-stars-rating-wordpress * https://github.com/ambionics/phpggc/issues/52 * https://blog.detectify.com/2019/07/23/improving-wordpress-plugin-security/ * https://i.blackhat.com/us-18/Thu-August-9/us-18-Thomas-Its-A-PHP-Unserialization-Vulnerability-Jim-But-Not-As-We-Know-It.pdf * https://cdn2.hubspot.net/hubfs/3853213/us-18-Thomas-It%27s-A-PHP-Unserialization-Vulnerability-Jim-But-Not-As-We-....pdf * https://2018.zeronights.ru/wp-content/uploads/materials/9%20ZN2018%20WV%20-%20PHP%20unserialize.pdf * https://medium.com/@knownsec404team/extend-the-attack-surface-of-php-deserialization-vulnerability-via-phar-d6455c6a1066#3c0f Originally fixed in WordPress 5.5.2: * https://github.com/WordPress/wordpress-develop/commit/add6bedf3a53b647d0ebda2970057912d3cd79d3 * https://wordpress.org/news/2020/10/wordpress-5-5-2-security-and-maintenance-release/ Related Security Advisories: * https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-28032 * https://nvd.nist.gov/vuln/detail/CVE-2020-28032 Notification to the Requests repo including a fix in: * https://github.com/rmccue/Requests/pull/421 and * https://github.com/rmccue/Requests/pull/422 ### For more information If you have any questions or comments about this advisory: * Open an issue in [Request](https://github.com/WordPress/Requests/) |
CVE-2021-29476
GHSA-52qp-jpq7-6c54 |
| VCID-fuma-nkmd-zkc1 | security update |
CVE-2019-17673
|
| VCID-gy54-apzn-7kef | security update |
CVE-2020-28036
|
| VCID-h5up-s13c-2ygg | security update |
CVE-2022-43497
|
| VCID-h97y-a92u-2fay | security update |
CVE-2020-28040
|
| VCID-hndb-7b4f-7bbw | security update |
CVE-2019-16223
|
| VCID-htec-cnsd-4ke4 | security update |
CVE-2022-21663
|
| VCID-htr5-ugyh-7yaz | security update |
CVE-2021-29447
|
| VCID-jjjw-sspg-q3c3 | security update |
CVE-2019-20041
|
| VCID-k52x-fa57-hkfk | security update |
CVE-2019-16219
|
| VCID-kk83-bnn5-tuar | security update |
CVE-2020-4048
|
| VCID-kn9s-5v5u-d3fj | security update |
CVE-2019-20043
|
| VCID-n7ne-unru-7fhn | security update |
CVE-2020-28035
|
| VCID-ngkc-cwzj-nbdk | security update |
CVE-2020-28033
|
| VCID-pkjb-8649-fqd2 | security update |
CVE-2020-28034
|
| VCID-psca-f78j-hbc2 | security update |
CVE-2020-28039
|
| VCID-pyzc-scrd-bufa | security update |
CVE-2020-11025
|
| VCID-q84d-utmc-g3fn | security update |
CVE-2020-25286
|
| VCID-r4qy-1wa6-t7gh | security update |
CVE-2019-17672
|
| VCID-sszr-mn9y-kkhg | WordPress Core, in versions up to 6.0.2, is vulnerable to Authenticated Stored Cross-Site Scripting that can be exploited by users with access to the WordPress post and page editor, typically consisting of Authors, Contributors, and Editors making it possible to inject arbitrary web scripts into posts and pages that execute if the the_meta(); function is called on that page. |
CVE-2022-4973
|
| VCID-tffx-7mmd-gkcf | security update |
CVE-2020-28038
|
| VCID-tgfm-2c63-d7dk | security update |
CVE-2020-4049
|
| VCID-u1fw-ahar-8uc1 | security update |
CVE-2020-4047
|
| VCID-v5s7-vwe3-5bak | security update |
CVE-2020-11029
|
| VCID-v7ph-mtd1-y3e1 | security update |
CVE-2022-43500
|
| VCID-w8w1-e5zu-ffgx | security update |
CVE-2020-11026
|
| VCID-wenb-bpws-mkar | security update |
CVE-2020-11028
|
| VCID-xfxs-pjex-3bh3 | security update |
CVE-2023-39999
|
| VCID-xzu6-fn31-43ej | security update |
CVE-2022-21662
|
| VCID-zmhc-4gku-13ga | security update |
CVE-2020-28037
|