CVE-2026-1336
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 · uneditedThe AI ChatBot with ChatGPT and Content Generator by AYS plugin for WordPress is vulnerable to unauthorized access and modification of data due to missing capability checks on the store_data() and get_chatgpt_api_key() functions in all versions up to, and including, 2.7.5. This makes it possible for unauthenticated attackers to view, modify or delete the plugin's ChatGPT API key. The vulnerability was partially fixed in version 2.7.5 and fully fixed in version 2.7.6
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 confidenceThe AI ChatBot with ChatGPT and Content Generator by AYS WordPress plugin versions up to 2.7.5 lack proper capability checks on the store_data() and get_chatgpt_api_key() functions, allowing unauthenticated attackers to view, modify, or delete the ChatGPT API key stored by 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check the installed plugin versionRun `wp plugin get ai-chatbot-ai-chatgpt-content-generator` via WP-CLI, or open the main plugin PHP file (usually ai-chatbot.php) and look at the plugin header comment for the Version fieldAffected if The version listed is 2.7.5 or lower
-
Verify the plugin is activeRun `wp plugin list --status=active --format=json` or check the WordPress admin Plugins pageAffected if The plugin is installed and active (inactive plugins still contain the vulnerable code but are not remotely exploitable)
-
Confirm the vulnerable functions exist in the codeInspect the plugin main file for the store_data() and get_chatgpt_api_key() functions and verify they lack current_user_can() or similar capability checksAffected if These functions exist and contain no authorization checks (they are present in versions 2.7.5 and below)
The environment is affected if the plugin version is 2.7.5 or lower and the plugin is active, since the vulnerable unauthenticated API key access functions are present in those versions.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate the plugin to version 2.7.6 or later to apply the full fix that adds proper authorization checks to the vulnerable functions.
2.7.6
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'AI ChatBot with ChatGPT and Content Generator by AYS' plugin
- Check if an update is available for the plugin
- If an update is available, click 'Update Now' to update to the latest version
- Alternatively, navigate to Dashboard > Updates and select the plugin to update
- Verify the plugin has been updated to version 2.7.6 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1336 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1336 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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