dbcve.org
Chatgpt AssistantWordPress extension · Ays Pro

CVE-2024-7713

HIGH · 7.5 CVSS v3.1 Published 2024-09-27
Fix available
A fix is available. Upgrade to 2.1.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 AI ChatBot with ChatGPT and Content Generator by AYS WordPress plugin before 2.1.0 discloses the Open AI API Key, allowing unauthenticated users to obtain it

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 AI ChatBot with ChatGPT and Content Generator by AYS WordPress plugin before version 2.1.0 contains an information disclosure vulnerability that allows unauthenticated users to retrieve the configured OpenAI API key, effectively exposing sensitive credentials to anyone.

MitigationUpdate the plugin to version 2.1.0 or later and immediately rotate any exposed OpenAI API keys to prevent unauthorized use of the associated OpenAI account.

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
Chatgpt AssistantWordPress extension
Affected:< 2.1.0

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

CVSS:3.1/AV:N/AC:L/PR:N/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 plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'AI ChatBot with ChatGPT and Content Generator by AYS' or 'Ays Pro Chatgpt Assistant'
    Affected if The plugin is installed and active
  2. Check plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find the AYS plugin, and compare the installed version against 2.1.0
    Affected if Installed version is less than 2.1.0
  3. Confirm API key is configured
    Navigate to the plugin settings (look for AYS ChatBot settings in the WordPress admin menu) and check if an OpenAI API key has been saved in the plugin configuration
    Affected if An OpenAI API key is stored in the plugin settings
  4. Test unauthenticated access to API key
    Send a request to the plugin's AJAX endpoint or REST API route that handles the chatbot functionality without providing any authentication credentials
    Affected if The endpoint returns the configured OpenAI API key to unauthenticated users

You are affected if the Ays Pro Chatgpt Assistant plugin is installed with a version below 2.1.0 and has an OpenAI API key configured in its settings, especially if that key is exposed to unauthenticated users.

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

Update the plugin to version 2.1.0 or later and immediately rotate any exposed OpenAI API keys to prevent unauthorized use of the associated OpenAI account.

Recommended fix High confidence

2.1.0

  1. Backup the WordPress database and files before making any changes
  2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins
  3. Locate 'AI ChatBot with ChatGPT and Content Generator by AYS' (Chatgpt Assistant)
  4. Click 'Update Now' if an update is available, or manually upload version 2.1.0 or later
  5. Verify the plugin updated successfully to version 2.1.0 or newer
  6. Confirm the OpenAI API key is no longer exposed by testing the plugin functionality
  7. Ensure the API key is stored securely in the plugin settings after update

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

Fix this in Chatgpt Assistant Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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