dbcve.org
AipowerWordPress extension

CVE-2023-51528

HIGH · 8.8 CVSS v3.1 Published 2024-02-29
Fix available
A fix is available. Upgrade to 1.8.13 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Senol Sahin AI Power: Complete AI Pack – Powered by GPT-4.This issue affects AI Power: Complete AI Pack – Powered by GPT-4: from n/a through 1.8.12.

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

Cross-Site Request Forgery (CSRF) vulnerability in the AI Power WordPress plugin allows attackers to trick authenticated administrators into performing unintended state-changing actions (such as modifying plugin settings or executing AI commands) by crafting malicious requests that the user's browser automatically submits due to missing or inadequate anti-CSRF token validation.

MitigationUpdate the AI Power plugin to a version beyond 1.8.12 where the CSRF vulnerability has been patched; alternatively, implement anti-CSRF nonces (WordPress nonces) on all state-changing forms and AJAX actions within the plugin.

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
AipowerWordPress extension
Affected:< 1.8.13

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Confirm AI Power plugin is installed
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'AI Power' or 'Aipower' in the list of active plugins
    Affected if AI Power plugin is present and active in the WordPress installation
  2. Identify installed version number
    In the Plugins list, click on 'Plugin Details' under AI Power, or inspect the plugin's main PHP file (commonly ai-power.php or similar in wp-content/plugins/aipower/) and read the Version header in the plugin comments
    Affected if The reported version is less than 1.8.13 (for example, 1.8.12, 1.8.11, etc.)
  3. Verify state-changing endpoints exist
    Review plugin files in wp-content/plugins/aipower/ for PHP files handling form submissions or AJAX actions (typically files containing '$_POST', '$_GET', or 'wp_ajax_' hooks) that modify settings or execute AI commands
    Affected if The plugin contains forms or AJAX handlers that perform state-changing operations (modifying options, executing AI generation, etc.)
  4. Inspect for CSRF token validation
    Open the PHP files handling state-changing requests and search for WordPress nonce verification functions such as 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' within the handler functions
    Affected if State-changing handlers lack nonce verification or contain inadequate validation (for example, nonce checks that are commented out, missing, or only performed conditionally)
  5. Confirm plugin is accessible to authenticated admins
    Verify the WordPress site allows administrator-level users who could be targeted by CSRF attacks, check user roles under Users > All Users in the admin panel
    Affected if Administrator or other high-privilege users exist on the WordPress site who could be socially engineered to trigger malicious requests

You are affected if AI Power plugin is installed with a version lower than 1.8.13 AND the plugin contains state-changing functionality (settings, AI commands) that lacks proper CSRF token (nonce) validation in its request handlers.

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 1.8.13 or later
Fixed in 1.8.13
Interim mitigation

Update the AI Power plugin to a version beyond 1.8.12 where the CSRF vulnerability has been patched; alternatively, implement anti-CSRF nonces (WordPress nonces) on all state-changing forms and AJAX actions within the plugin.

Recommended fix High confidence

1.8.13

  1. Update the AI Power plugin to version 1.8.13 or later through the WordPress admin dashboard
  2. Navigate to Dashboard > Updates or Plugins > All Plugins
  3. Locate 'AI Power: Complete AI Pack – Powered by GPT-4'
  4. Click 'Update Now' or enable automatic updates for this plugin
  5. Verify the update was successful by checking the installed version number matches 1.8.13 or higher

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

Fix this in Aipower Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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 locally
dbcve dependency scanner

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