HomeWordPress vulnerabilitiesWP-PostRatings
WP-PostRatings vulnerabilities
WP-PostRatings has 3 known vulnerabilities in this database. The most recent published record is dated 16 Jan 2024.
- Known vulnerabilities
- 3
- Active installs
- 20,000+
- Latest version
- 2.0.2
- Last updated
- 1 Sep 2026
- Most recent
- 16 Jan 2024
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 |
|---|---|---|---|---|
| Cross-site request forgery (CSRF) CVE-2021-25117 | Medium 4.8 | Before 1.86.1 | Fixed in 1.86.1 | 16 Jan 2024 |
| Security weakness CVE-2022-36422 | Medium 4.3 | Up to 1.89 | Fixed in a later version (latest 2.0.2) | 9 Sep 2022 |
| SQL injection CVE-2011-4646 | Not scored | Before 1.62 | Fixed in 1.62 | 30 Nov 2011 |
Read the published descriptions
- CVE-2021-25117, 16 Jan 2024
- The WP-PostRatings WordPress plugin before 1.86.1 does not sanitise the postratings_image parameter from its options page (wp-admin/admin.php?page=wp-postratings/postratings-options.php). Even though the page is only accessible to administrators, and protected against CSRF attacks, the issue is still exploitable when the unfiltered_html capability is disabled. CVE record
- CVE-2022-36422, 9 Sep 2022
- Rating increase/decrease via race condition in Lester 'GaMerZ' Chan WP-PostRatings plugin <= 1.89 at WordPress. CVE record
- CVE-2011-4646, 30 Nov 2011
- SQL injection vulnerability in wp-postratings.php in the WP-PostRatings plugin 1.50, 1.61, and probably other versions before 1.62 for WordPress allows remote authenticated users with the Author role to execute arbitrary SQL commands via the id attribute of the ratings shortcode when creating a post. NOTE: some of these details are obtained from third party information. CVE record
What to do if you run WP-PostRatings
If you run WP-PostRatings, 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-PostRatings vulnerabilities
Free. We email you when a new vulnerability is published for WP-PostRatings, 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.