dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-45435

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Melapress WP Activity Log allows DOM-Based XSS. This issue affects WP Activity Log: from n/a through 5.6.3.

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 confidence

DOM-Based XSS vulnerability in the Melapress WP Activity Log WordPress plugin (versions up to 5.6.3) allows authenticated attackers to inject malicious JavaScript into the plugin's activity log interface. The vulnerability stems from improper sanitization of user-supplied input that is processed by client-side JavaScript and reflected in the DOM without appropriate encoding.

MitigationUpdate WP Activity Log to version 5.6.4 or later which contains the security fix. Until patched, limit administrative access and monitor for suspicious activity involving the plugin.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP Activity Log plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Activity Log' or check the plugins directory via FTP/SSH for /wp-content/plugins/wp-activity-log/
    Affected if Plugin is installed and active
  2. Determine installed plugin version
    In WordPress admin, find WP Activity Log in Plugins > Installed Plugins and check the version number displayed beneath the plugin name, or read version from the plugin's main PHP file header comment
    Affected if Version is 5.6.3 or lower (any version through 5.6.3)
  3. Check if untrusted users can access the plugin
    Review WordPress user roles with access to WP Activity Log functionality (Users > Users and check role capabilities, or check plugin settings under Activity Log > Roles and Capabilities)
    Affected if Users with limited privileges (subscriber, contributor, or non-admin) can access or view activity logs
  4. Identify if user-supplied input fields are present in plugin pages
    Navigate to WP Activity Log pages in the admin dashboard and inspect any forms, search fields, or input parameters that accept user data and display it back on the page
    Affected if Plugin displays user-supplied data (usernames, IP addresses, search queries) directly in the DOM without visible sanitization

You are affected if WP Activity Log plugin versions through 5.6.3 is installed and active, and untrusted users can provide input that gets rendered to the page.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WP Activity Log to version 5.6.4 or later which contains the security fix. Until patched, limit administrative access and monitor for suspicious activity involving the plugin.

Recommended fix Moderate confidence

Upgrade WP Activity Log to the latest available version (higher than 5.6.3)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'WP Activity Log' plugin by Melapress
  4. 4. Check the current installed version (should be 5.6.3 or below)
  5. 5. If an update is available, click 'Update Now' to upgrade to the latest version
  6. 6. After updating, verify the plugin version has changed to confirm the update was successful
  7. 7. Test the plugin functionality to ensure the upgrade did not break any features
Caveat Review plugin changelog for any breaking changes between current version and latest release before upgrading in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45435 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45435 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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