HomeWordPress vulnerabilitiesWP Popular Posts
WP Popular Posts vulnerabilities
WP Popular Posts has 7 known vulnerabilities in this database. The most recent published record is dated 1 Oct 2026.
- Known vulnerabilities
- 7
- Active installs
- 100,000+
- Latest version
- 7.4.3
- Last updated
- 27 Sep 2026
- Most recent
- 1 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Sensitive data exposure CVE-2026-92548 | Medium 5.3 | Up to 7.4.2 | Fixed in a later version (latest 7.4.3) | 6 d ago |
| Remote code execution CVE-2024-11733 | High 7.3 | Up to 7.1.0 | Fixed in a later version (latest 7.4.3) | 3 Jan 2025 |
| Cross-site scripting (XSS) CVE-2023-45607 | Medium 6.5 | Before 6.3.3 | Fixed in 6.3.3 | 18 Oct 2023 |
| Security weakness CVE-2022-43468 | High 7.5 | Up to 6.0.5 | Fixed in a later version (latest 7.4.3) | 7 Dec 2022 |
| Remote code execution CVE-2021-42362 | High 8.8 | Up to 5.3.2 | Fixed in a later version (latest 7.4.3) | 17 Nov 2021 |
| Cross-site scripting (XSS) CVE-2021-36872 | Medium 5.5 | Up to 5.3.3 | Fixed in a later version (latest 7.4.3) | 23 Sep 2021 |
| Cross-site scripting (XSS) CVE-2021-20746 | Medium 5.4 | Up to 5.3.2 | Fixed in a later version (latest 7.4.3) | 28 Jun 2021 |
Read the published descriptions
- CVE-2026-92548, 1 Oct 2026
- The WP Popular Posts plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 7.4.2 via the 'context' parameter. This makes it possible for unauthenticated attackers to extract sensitive edit-context fields - including raw title, raw content body, password, meta, status, and guid - from non-public post objects such as wp_block synced patterns that WordPress core itself refuses to expose to unauthenticated callers. This is possible because the plugin's REST route is registered with a permission_callback of __return_true and passes the caller-supplied context parameter (e.g., context=edit) directly to WP_REST_Posts_Controller::prepare_item_for_response() without invoking get_item_permissions_check() or check_read_permission(), while the underlying query accepts an arbitrary post_type value without enforcing public or show_in_rest visibility flags. CVE record
- CVE-2024-11733, 3 Jan 2025
- The The WordPress Popular Posts plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 7.1.0. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes. CVE record
- CVE-2023-45607, 18 Oct 2023
- Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Hector Cabrera WordPress Popular Posts plugin <= 6.3.2 versions. CVE record
- CVE-2022-43468, 7 Dec 2022
- External initialization of trusted variables or data stores vulnerability exists in WordPress Popular Posts 6.0.5 and earlier, therefore the vulnerable product accepts untrusted external inputs to update certain internal variables. As a result, the number of views for an article may be manipulated through a crafted input. CVE record
- CVE-2021-42362, 17 Nov 2021
- The WordPress Popular Posts WordPress plugin is vulnerable to arbitrary file uploads due to insufficient input file type validation found in the ~/src/Image.php file which makes it possible for attackers with contributor level access and above to upload malicious files that can be used to obtain remote code execution, in versions up to and including 5.3.2. CVE record
- CVE-2021-36872, 23 Sep 2021
- Authenticated Persistent Cross-Site Scripting (XSS) vulnerability in WordPress Popular Posts plugin (versions <= 5.3.3). Vulnerable at &widget-wpp[2][post_type]. CVE record
- CVE-2021-20746, 28 Jun 2021
- Cross-site scripting vulnerability in WordPress Popular Posts 5.3.2 and earlier allows a remote authenticated attacker to inject an arbitrary script via unspecified vectors. CVE record
What to do if you run WP Popular Posts
If you run WP Popular Posts, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WP Popular Posts vulnerabilities
Free. We email you when a new vulnerability is published for WP Popular Posts, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.