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

HomeWordPress vulnerabilitiesWP Activity Log

WP Activity Log vulnerabilities

WP Activity Log has 8 known vulnerabilities in this database. The most recent published record is dated 25 Jun 2026.

Known vulnerabilities
8
Active installs
300,000+
Latest version
5.6.7
Last updated
23 Sep 2026
Most recent
25 Jun 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
Cross-site scripting (XSS)
CVE-2026-56005
High 7.1Up to 5.6.3.1Fixed in a later version (latest 5.6.7)25 Jun 2026
Cross-site scripting (XSS)
CVE-2025-0924
High 7.2Before 5.3.0Fixed in 5.3.017 Feb 2025
Cross-site scripting (XSS)
CVE-2024-10793
High 7.2Before 5.2.2Fixed in 5.2.215 Nov 2024
Cross-site request forgery (CSRF)
CVE-2023-2286
Medium 4.3Up to 4.5.0Fixed in a later version (latest 5.6.7)9 Jun 2023
Broken access control
CVE-2023-2261
Medium 4.3Up to 4.5.0Fixed in a later version (latest 5.6.7)9 Jun 2023
Broken access control
CVE-2020-36716
High 7.3Up to 4.0.1Fixed in a later version (latest 5.6.7)7 Jun 2023
Cross-site request forgery (CSRF)
CVE-2014-5072
High 8.8Before 1.2.5Fixed in 1.2.56 Apr 2018
Security weakness
CVE-2018-8719
Medium 5.3Not yet publishedCheck for an update4 Apr 2018
Read the published descriptions
CVE-2026-56005, 25 Jun 2026
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Melapress WP Activity Log wp-security-audit-log allows Stored XSS.This issue affects WP Activity Log: from n/a through 5.6.3.1. CVE record
CVE-2025-0924, 17 Feb 2025
The WP Activity Log plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘message’ parameter in all versions up to, and including, 5.2.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
CVE-2024-10793, 15 Nov 2024
The WP Activity Log plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the user_id parameter in all versions up to, and including, 5.2.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever an administrative user accesses an injected page. CVE record
CVE-2023-2286, 9 Jun 2023
The WP Activity Log for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.5.0. This is due to missing or incorrect nonce validation on the ajax_run_cleanup function. This makes it possible for unauthenticated attackers to invoke this function via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
CVE-2023-2261, 9 Jun 2023
The WP Activity Log plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the handle_ajax_call function in versions up to, and including, 4.5.0. This makes it possible for authenticated attackers, with subscriber-level access or higher, to obtain a list of users with accounts on the site. This includes ids, usernames and emails. CVE record
CVE-2020-36716, 7 Jun 2023
The WP Activity Log plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the setup_page function in versions up to, and including, 4.0.1. This makes it possible for unauthenticated attackers to run the setup wizard (if it has not been run previously) and access plugin configuration options. CVE record
CVE-2014-5072, 6 Apr 2018
Cross-site request forgery (CSRF) vulnerability in WP Security Audit Log plugin before 1.2.5 for WordPress allows remote attackers to hijack the authentication of unspecified victims via unknown vectors. CVE record
CVE-2018-8719, 4 Apr 2018
An issue was discovered in the WP Security Audit Log plugin 3.1.1 for WordPress. Access to wp-content/uploads/wp-security-audit-log/* files is not restricted. For example, these files are indexed by Google and allows for attackers to possibly find sensitive information. CVE record

What to do if you run WP Activity Log

If you run WP Activity Log, 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 Activity Log vulnerabilities

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