dbcve.org
Wp Activity LogWordPress extension · Melapress

CVE-2024-2018

HIGH · 8.8 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 4.6.4.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
The WP Activity Log Premium plugin for WordPress is vulnerable to SQL Injection via the entry->roles parameter in all versions up to, and including, 4.6.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers with subscriber privileges to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. One demonstrated attack included the injection of a PHP Object.

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 confidence

The WP Activity Log Premium plugin for WordPress contains a SQL injection vulnerability in the entry->roles parameter in versions up to 4.6.4. The vulnerability stems from insufficient escaping of user-supplied input combined with a lack of prepared statements in the underlying SQL query. Authenticated attackers with subscriber-level privileges can inject arbitrary SQL commands, potentially extracting sensitive database information or injecting PHP objects.

MitigationUpdate the WP Activity Log Premium plugin to a version beyond 4.6.4 to receive the vendor patch that addresses proper parameter escaping and SQL query preparation.

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
Affected:< 4.6.4.1

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 the installed version of the WP Activity Log plugin
    Navigate to WordPress Admin > Plugins and locate 'WP Activity Log' or 'Melapress WP Activity Log' in the installed plugins list. Check the version number displayed under the plugin name.
    Affected if The displayed version number is earlier than 4.6.4.1 (for example, 4.6.4, 4.6.3, 4.5.x, etc.)
  2. Confirm the plugin is active on the site
    In WordPress Admin > Plugins, verify that the WP Activity Log plugin shows as 'Active'. The vulnerability only applies when the plugin is actively running.
    Affected if The plugin is installed and active with a version below 4.6.4.1
  3. Identify WordPress user roles with subscriber-level access
    Go to WordPress Admin > Users > User Roles or inspect the wp_options table for the wp_user_roles entry. Identify if any users are assigned the 'Subscriber' role or any custom role with equivalent low-level privileges.
    Affected if Any Subscriber-level or low-privilege user accounts exist on the site while the plugin version is below 4.6.4.1
  4. Review database query logs for suspicious activity (optional)
    Check server error logs, WordPress debug logs, or any SQL query logging plugins for unusual database queries originating from the WP Activity Log plugin, particularly queries containing unexpected SQL operators or payloads in role-related parameters.
    Affected if Unexpected or malicious SQL syntax appears in logs tied to activity log functionality with a version below 4.6.4.1

A site is affected if the Melapress WP Activity Log plugin is active at a version below 4.6.4.1 and any subscriber-level or low-privilege user accounts exist on the WordPress installation.

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
Upgrade available Upgrade to 4.6.4.1 or later
Fixed in 4.6.4.1
Interim mitigation

Update the WP Activity Log Premium plugin to a version beyond 4.6.4 to receive the vendor patch that addresses proper parameter escaping and SQL query preparation.

Recommended fix High confidence

WP Activity Log version 4.6.4.1

  1. Backup your WordPress database and files before making any changes
  2. Log in to WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate WP Activity Log plugin
  5. Click 'Update Now' if an update is available, or manually upload version 4.6.4.1
  6. Verify the plugin version after update to confirm 4.6.4.1 is installed
  7. Test that the activity logging functionality works correctly

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
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2018 — 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-2024-2018 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