Wp Activity LogWordPress extension · Melapress
CVE-2024-10793
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WP Activity Log plugin for WordPress versions up to 5.2.1 contains a stored XSS vulnerability in the user_id parameter due to insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject malicious scripts that execute when administrators access affected pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp Activity LogWordPress extension
< 5.2.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify WP Activity Log plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins, or check the wp-content/plugins/wp-activity-log directory exists and contains plugin filesAffected if The WP Activity Log plugin by Melapress is present in the WordPress installation
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > WP Activity Log and view the version number displayed, or read the main plugin PHP file (e.g., wp-activity-log.php) and look for the 'Version:' header commentAffected if The version number is less than 5.2.2 (e.g., 5.2.1, 5.2.0, or earlier)
-
Identify user_id parameter usage in pluginSearch plugin files for occurrences of 'user_id' in GET/POST request handling code, particularly in views that display user information to administrators such as activity logs, user reports, or dashboard widgetsAffected if The plugin processes user_id parameter without sanitization and displays it in admin pages
-
Check database for injected scriptsQuery the WordPress database (wp_postmeta, wp_options, or custom activity log tables) for any records containing suspicious script tags, javascript: URIs, or onload/onerror attributes in user_id related fieldsAffected if Malicious JavaScript code is found stored in the database related to user_id entries that would execute when viewed by administrators
You are affected if the WP Activity Log plugin version is below 5.2.2 and the user_id parameter is being used in the plugin's admin interface, or if malicious scripts are already stored in the database from exploitation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.2.2
Update the WP Activity Log plugin to version 5.2.2 or later which contains the official patch, or implement proper sanitization of the user_id parameter and output escaping before rendering.
5.2.2
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find WP Activity Log in the list
- Click 'Update now' when an update is available, or manually update to version 5.2.2
- Verify the update completed successfully by checking the plugin version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Activity Log
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10793 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-10793 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data