dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-13378

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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 plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.7.0 via the ays_chatgpt_pinecone_upsert function. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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 · moderate confidence

The AI ChatBot plugin for WordPress contains an SSRF vulnerability in the ays_chatgpt_pinecone_upsert function, allowing unauthenticated attackers to induce the server to make arbitrary HTTP requests to internal or external resources. The function likely accepts a user-controllable URL or hostname parameter without proper validation, enabling attackers to access internal services, port scan internal networks, or exfiltrate data.

MitigationUpdate the plugin to the latest version immediately to patch the SSRF vulnerability. Additionally, implement network-level controls (WAF rules, egress filtering) to restrict outbound requests from the web server and add strict allowlist validation for any URL/hostname parameters in the affected function.

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
Low
Integrity
Low
Availability
None

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

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

  1. Verify AI ChatBot plugin is installed
    Log in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'AI ChatBot' or 'ays-chatbot' in the plugin list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'ays-chatbot' or similar.
    Affected if The AI ChatBot plugin by or among us is installed and active on the WordPress site.
  2. Determine the installed plugin version
    In the WordPress admin panel, click on the plugin name in the installed plugins list to view version details. Alternatively, open the main plugin file (e.g., ays-chatbot.php) in /wp-content/plugins/ays-chatbot/ and look for the 'Version' header in the file comments.
    Affected if The installed version is lower than the patched version released after CVE-2025-13378 was addressed.
  3. Identify if the vulnerable endpoint is exposed
    Check if the WordPress REST API or admin-ajax.php endpoint handling the 'ays_chatgpt_pinecone_upsert' action is accessible. This typically involves checking the plugin's AJAX handlers or custom REST routes defined in the plugin's PHP files.
    Affected if The plugin exposes an AJAX or REST endpoint that calls the ays_chatgpt_pinecone_upsert function without authentication.
  4. Inspect plugin configuration for Pinecone integration
    Navigate to the plugin settings in WordPress admin (usually under AI ChatBot settings). Look for any configuration related to Pinecone vector database integration, as this is the feature that triggers the vulnerable function.
    Affected if The Pinecone integration feature is enabled in the plugin settings, allowing user-controllable URL or API endpoint input.

If the AI ChatBot plugin is installed and the ays_chatgpt_pinecone_upsert function is accessible without authentication while the plugin version has not been patched for CVE-2025-13378, the environment is affected by this SSRF vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version immediately to patch the SSRF vulnerability. Additionally, implement network-level controls (WAF rules, egress filtering) to restrict outbound requests from the web server and add strict allowlist validation for any URL/hostname parameters in the affected function.

Recommended fix Moderate confidence

Plugin version higher than 2.7.0 (latest stable release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'AI ChatBot with ChatGPT and Content Generator by AYS'
  4. If an update is available, click 'Update Now'
  5. After updating, verify the plugin version is above 2.7.0

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,310
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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