Echo Knowledge Base at a glance
- 4 publicly disclosed vulnerabilities, 2 of them rated High or Critical. The most recent was disclosed on Oct 27, 2026.
- Ranked #1662 by popularity on WordPress.org (10,000+ active installs).
- The latest version is 17.320.0 (released Nov 8, 2026). The most recent security fix shipped in 17.311.0.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Echo Knowledge Base version
Enter the Echo Knowledge Base version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Echo Knowledge Base”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Echo Knowledge Base”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (17.320.0). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Echo Knowledge Base vulnerabilities
Echo Knowledge Base <= 17.214.0 - Reflected Cross-Site Scripting via 'new_kb_config' Parameter
Cross-site scripting (XSS) · CVE-2026-101935
Affected versions: ≤ 17.214.0
Fixed in: 17.311.0
Severity: Medium 6.1 · Disclosed Oct 27, 2026
Knowledge Base for Documentation, FAQs with AI Assistance <= 17.211.0 - Unauthenticated Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2026-28187
Affected versions: ≤ 17.211.0
Fixed in: 17.212.0
Severity: High 7.2 · Disclosed Aug 13, 2026
Echo Knowledge Base – Documentation, FAQs, AI Chat & AI Search <= 16.011.0 - Missing Authorization
Missing authorization · CVE-2026-25402
Affected versions: ≤ 16.011.0
Fixed in: 16.20.0
Severity: Medium 4.3 · Disclosed Jan 29, 2026
Knowledge Base for Documentation, FAQs with AI Assistance <= 11.30.2 - Unauthenticated PHP Object Injection in is_article_recently_viewed
PHP object injection · CVE-2024-24842
Affected versions: ≤ 11.30.2
Fixed in: 11.31.0
Severity: Critical 9.8 · Disclosed Feb 2, 2024
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Echo Knowledge Base <= 17.214.0 - Reflected Cross-Site Scripting via 'new_kb_config' ParameterCross-site scripting (XSS) · CVE-2026-101935 | ≤ 17.214.0 | 17.311.0 | Medium 6.1 | Oct 27, 2026 |
| Knowledge Base for Documentation, FAQs with AI Assistance <= 17.211.0 - Unauthenticated Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2026-28187 | ≤ 17.211.0 | 17.212.0 | High 7.2 | Aug 13, 2026 |
| Echo Knowledge Base – Documentation, FAQs, AI Chat & AI Search <= 16.011.0 - Missing AuthorizationMissing authorization · CVE-2026-25402 | ≤ 16.011.0 | 16.20.0 | Medium 4.3 | Jan 29, 2026 |
| Knowledge Base for Documentation, FAQs with AI Assistance <= 11.30.2 - Unauthenticated PHP Object Injection in is_article_recently_viewedPHP object injection · CVE-2024-24842 | ≤ 11.30.2 | 11.31.0 | Critical 9.8 | Feb 2, 2024 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 27, 2026.
Most common weaknesses in Echo Knowledge Base
Cross-site scripting (XSS)
2 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Missing authorization
1 issue
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
PHP object injection
1 issue
Specially crafted data makes the server behave in unintended ways. Combined with the right conditions, it can lead to a full takeover.
Frequently asked questions
Is Echo Knowledge Base safe to use?
Echo Knowledge Base is a well-known plugin with 10,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (17.320.0) and turn on automatic updates.
How do I find which version of Echo Knowledge Base my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesEcho Knowledge Base on WordPress.org