dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-3436

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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 coreActivity: Activity Logging for WordPress plugin for WordPress is vulnerable to SQL Injection via the 'order' and 'orderby' parameters in all versions up to, and including, 2.7 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-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 coreActivity WordPress plugin versions up to 2.7 are vulnerable to SQL Injection via the 'order' and 'orderby' parameters. Insufficient escaping of user-supplied input combined with lack of prepared statements in the existing SQL query allows authenticated attackers with Subscriber-level access or higher to inject arbitrary SQL commands and extract sensitive database information.

MitigationUpgrade the coreActivity plugin to version 2.8 or later, which contains the fix for proper input sanitization and prepared statement usage. If immediate upgrade is not possible, implement input validation on orderby/order parameters as a temporary workaround.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

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

  1. Verify coreActivity plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate coreActivity in the list. Alternatively, check the /wp-content/plugins/ directory for the coreactivity folder.
    Affected if coreActivity plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, click on the coreActivity plugin to view its details and version number. Or inspect the main plugin file (e.g., coreactivity.php) and look for the version header comment.
    Affected if Version is 2.7 or earlier (any version up to and including 2.7)
  3. Confirm WordPress user role access
    Check if any WordPress user accounts exist with Subscriber-level access or higher. Navigate to Users > All Users in WordPress admin to review existing user roles.
    Affected if At least one user account with Subscriber, Contributor, Author, Editor, or Administrator role exists
  4. Verify plugin exposes orderby/order functionality
    Locate PHP files in the coreActivity plugin that handle HTTP requests with 'order' or 'orderby' parameters. Search plugin source code for $_GET or $_REQUEST usage of these parameters in SQL query contexts.
    Affected if Plugin code processes 'order' or 'orderby' GET/POST parameters without using prepared statements
  5. Inspect database query code for SQL injection vulnerability
    Examine the specific PHP files handling database queries that incorporate orderby/order parameters. Look for direct string concatenation of these parameters into SQL queries instead of parameterized queries or proper escaping.
    Affected if SQL queries directly concatenate orderby/order parameters without $wpdb->prepare() or equivalent prepared statements

User is affected if coreActivity plugin version 2.7 or earlier is installed, active, and accessible to authenticated users with Subscriber-level access or higher.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the coreActivity plugin to version 2.8 or later, which contains the fix for proper input sanitization and prepared statement usage. If immediate upgrade is not possible, implement input validation on orderby/order parameters as a temporary workaround.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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