HomeWordPress vulnerabilitiesActivity Log
Activity Log vulnerabilities
Activity Log has 5 known vulnerabilities in this database. The most recent published record is dated 21 Nov 2024.
- Known vulnerabilities
- 5
- Active installs
- 200,000+
- Latest version
- 2.15.0
- Last updated
- 7 Sep 2026
- Most recent
- 21 Nov 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 scripting (XSS) CVE-2024-10788 | High 7.2 | Before 2.11.2 | Fixed in 2.11.2 | 21 Nov 2024 |
| CSV injection CVE-2022-27858 | High 7.4 | Before 2.8.4 | Fixed in 2.8.4 | 8 Nov 2022 |
| Cross-site scripting (XSS) CVE-2016-10890 | Medium 6.1 | Before 2.3.2 | Fixed in 2.3.2 | 21 Aug 2019 |
| Cross-site scripting (XSS) CVE-2016-10891 | Medium 6.1 | Before 2.3.3 | Fixed in 2.3.3 | 21 Aug 2019 |
| Cross-site scripting (XSS) CVE-2018-8729 | Medium 6.1 | Before 2.4.1 | Fixed in 2.4.1 | 15 Mar 2018 |
Read the published descriptions
- CVE-2024-10788, 21 Nov 2024
- The Activity Log - Monitor & Record User Changes plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the event parameters in all versions up to, and including, 2.11.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-2022-27858, 8 Nov 2022
- CSV Injection vulnerability in Activity Log Team Activity Log <= 2.8.3 on WordPress. CVE record
- CVE-2016-10890, 21 Aug 2019
- The aryo-activity-log plugin before 2.3.2 for WordPress has XSS. CVE record
- CVE-2016-10891, 21 Aug 2019
- The aryo-activity-log plugin before 2.3.3 for WordPress has XSS. CVE record
- CVE-2018-8729, 15 Mar 2018
- Multiple cross-site scripting (XSS) vulnerabilities in the Activity Log plugin before 2.4.1 for WordPress allow remote attackers to inject arbitrary JavaScript or HTML via a title that is not escaped. CVE record
What to do if you run Activity Log
If you run 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 Activity Log vulnerabilities
Free. We email you when a new vulnerability is published for 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.