Website support, maintenance and fixes for UK businessesCall 0208 088 8371info@websupportservices.co.uk

HomeWordPress vulnerabilitiesWP Post Author

WP Post Author vulnerabilities

WP Post Author has 7 known vulnerabilities in this database. The most recent published record is dated 29 Oct 2026.

Known vulnerabilities
7
Active installs
10,000+
Latest version
4.2.0
Last updated
20 Oct 2026
Most recent
29 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.

VulnerabilitySeverityAffectedFixPublished
Broken access control
CVE-2026-108685
Low 3.7Before 4.2.0Fixed in 4.2.029 Oct 2026
Sensitive data exposure
CVE-2026-108686
Low 3.7Before 4.2.0Fixed in 4.2.029 Oct 2026
SQL injection
CVE-2026-108125
High 7.1Before 4.1.0Fixed in 4.1.09 Oct 2026
SQL injection
CVE-2026-108124
Medium 4.9Before 4.1.0Fixed in 4.1.09 Oct 2026
SQL injection
CVE-2026-42708
High 7.6Up to 4.0.0Fixed in a later version (latest 4.2.0)7 Oct 2026
SQL injection
CVE-2026-11977
Medium 6.5Up to 3.9.1Fixed in a later version (latest 4.2.0)5 Aug 2026
SQL injection
CVE-2024-8757
High 7.2Up to 3.8.1Fixed in a later version (latest 4.2.0)12 Oct 2024
Read the published descriptions
CVE-2026-108685, 29 Oct 2026
The WP Post Author WordPress plugin before 4.2.0 does not check that the account was created before updating its profile during front-end registration, allowing unauthenticated users to overwrite the display name, nickname and website of the first user account, which is normally the administrator, when a registration form declares one of those fields. CVE record
CVE-2026-108686, 29 Oct 2026
The WP Post Author WordPress plugin before 4.2.0 does not restrict the integration settings it returns to visitors, allowing unauthenticated users to read the reCAPTCHA secret key when one has been saved. CVE record
CVE-2026-108125, 9 Oct 2026
Improper neutralization of special elements used in an SQL command ('SQL injection') vulnerability in wp-post-author. This issue affects wp-post-author version 4.0.0 prior to 4.1.0. CVE record
CVE-2026-108124, 9 Oct 2026
Improper neutralization of special elements used in an SQL command ('SQL injection') vulnerability in wp-post-author. This issue affects wp-post-author before 4.1.0. CVE record
CVE-2026-42708, 7 Oct 2026
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in AF themes WP Post Author wp-post-author allows Blind SQL Injection.This issue affects WP Post Author: from n/a through 4.0.0. CVE record
CVE-2026-11977, 5 Aug 2026
The WP Post Author - Author Box, Multiple Authors, Guest Authors & Custom Avatars plugin for WordPress is vulnerable to generic SQL Injection via the 'wpma_metabox_authors_list' parameter in all versions up to, and including, 3.9.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with author-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation is a two-step chain: an attacker first saves a crafted guest-author token via the wpma_metabox_authors_list parameter during post creation or editing, then triggers the injection when any admin user loads the post list screen at /wp-admin/edit.php, causing the injected SQL result to be rendered in the Authors column. CVE record
CVE-2024-8757, 12 Oct 2024
The WP Post Author - Boost Your Blog's Engagement with Author Box, Social Links, Co-Authors, Guest Authors, Post Rating System, and Custom User Registration Form Builder plugin for WordPress is vulnerable to time-based SQL Injection via the linked_user_id parameter in all versions up to, and including, 3.8.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record

What to do if you run WP Post Author

If you run WP Post Author, 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 Post Author vulnerabilities

Free. We email you when a new vulnerability is published for WP Post Author, 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.

Get website support