CVE-2026-56005
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 · uneditedSubscriber Cross Site Scripting (XSS) in WP Activity Log <= 5.6.3.1 versions.
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 · moderate confidenceA stored Cross-Site Scripting (XSS) vulnerability in the WP Activity Log plugin for WordPress allows authenticated subscribers to inject malicious JavaScript through plugin inputs. The vulnerability exists in versions 5.6.3.1 and below, allowing attackers with subscriber-level privileges to execute arbitrary scripts in the context of other users' browsers when they view activity logs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 versionIn WordPress admin, go to Plugins > Installed Plugins and locate WP Activity Log. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file header or the readme.txt file for the Version field.Affected if The installed version is 5.6.3.1 or lower.
-
Confirm subscriber-level user accounts existNavigate to Users > All Users in WordPress admin. Look for users with the Subscriber role. Alternatively, query the wp_usermeta table where meta_key = 'wp_capabilities' and meta_value contains 'subscriber'.Affected if There is at least one user with subscriber-level privileges.
-
Check if subscribers can access activity logsExamine the WP Activity Log plugin settings under Settings > WP Activity Log. Verify if there are role-based access controls that allow subscribers to view or create activity log entries.Affected if Subscribers have permission to create or view activity log entries.
-
Inspect activity logs for XSS payloadsNavigate to WP Activity Log > Activity Log. Review recent entries for script tags, javascript: URLs, onload/onerror attributes, or encoded XSS patterns. Check both log content and metadata fields.Affected if Activity logs contain unsanitized JavaScript code in user-related fields.
You are affected if the WP Activity Log plugin version is 5.6.3.1 or below AND at least one subscriber-level account exists with the ability to create or view activity log entries.
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.
From vendor dataUpdate WP Activity Log plugin to a version newer than 5.6.3.1. If no update is available, disable the plugin until a patch is released, or implement input sanitization/validation on plugin outputs and consider a WAF rule to filter XSS payloads.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56005 — 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-2026-56005 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