FeedWordPress at a glance
- 6 publicly disclosed vulnerabilities, 2 of them rated High or Critical. The most recent was disclosed on Oct 30, 2026.
- Ranked #2320 by popularity on WordPress.org (8,000+ active installs).
- The latest version is 2026.1030 (released Oct 30, 2026). The most recent security fix shipped in 2026.1016.
- 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 FeedWordPress version
Enter the FeedWordPress 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 “FeedWordPress”, 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 “FeedWordPress”.
- 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 (2026.1030). 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 FeedWordPress vulnerabilities
FeedWordPress <= 2026.0517 - Unauthenticated Stored Cross-Site Scripting via Syndicated Feed Content
Cross-site scripting (XSS) · CVE-2026-110530
Affected versions: ≤ 2026.0517
Fixed in: 2026.1016
Severity: High 7.2 · Disclosed Oct 30, 2026
FeedWordPress <= 2022.0222 - Insecure Direct Object Referece
Missing authorization · CVE-2024-0839
Affected versions: ≤ 2022.0222
Fixed in: 2024.0428
Severity: Medium 5.3 · Disclosed Mar 4, 2024
FeedWordPress <= 2021.0713 - Reflected Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2021-25055
Affected versions: ≤ 2021.0713
Fixed in: 2022.0123
Severity: Medium 6.1 · Disclosed Jan 18, 2022
FeedWordPress < 2015.0514 - SQL Injection
SQL injection · CVE-2015-4018
Affected versions: < 2015.0514
Fixed in: 2015.0514
Severity: Critical 9.8 · Disclosed May 19, 2015
FeedWordPress < 2015.0514 - Reflected Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2015-9358
Affected versions: < 2015.0514
Fixed in: 2015.0514
Severity: Medium 6.1 · Disclosed May 14, 2015
FeedWordPress < 2015.0426 - Cross-Site Scripting
Cross-site scripting (XSS)
Affected versions: ≤ 2014.0805
Fixed in: 2015.0426
Severity: Medium 6.1 · Disclosed Apr 26, 2015
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| FeedWordPress <= 2026.0517 - Unauthenticated Stored Cross-Site Scripting via Syndicated Feed ContentCross-site scripting (XSS) · CVE-2026-110530 | ≤ 2026.0517 | 2026.1016 | High 7.2 | Oct 30, 2026 |
| FeedWordPress <= 2022.0222 - Insecure Direct Object RefereceMissing authorization · CVE-2024-0839 | ≤ 2022.0222 | 2024.0428 | Medium 5.3 | Mar 4, 2024 |
| FeedWordPress <= 2021.0713 - Reflected Cross-Site ScriptingCross-site scripting (XSS) · CVE-2021-25055 | ≤ 2021.0713 | 2022.0123 | Medium 6.1 | Jan 18, 2022 |
| FeedWordPress < 2015.0514 - SQL InjectionSQL injection · CVE-2015-4018 | < 2015.0514 | 2015.0514 | Critical 9.8 | May 19, 2015 |
| FeedWordPress < 2015.0514 - Reflected Cross-Site ScriptingCross-site scripting (XSS) · CVE-2015-9358 | < 2015.0514 | 2015.0514 | Medium 6.1 | May 14, 2015 |
| FeedWordPress < 2015.0426 - Cross-Site ScriptingCross-site scripting (XSS) | ≤ 2014.0805 | 2015.0426 | Medium 6.1 | Apr 26, 2015 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 30, 2026.
Most common weaknesses in FeedWordPress
Cross-site scripting (XSS)
4 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.
SQL injection
1 issue
Input such as a form field can be used to rewrite the queries the site sends to its database. Attackers use it to pull out customer, member or order data.
Frequently asked questions
Is FeedWordPress safe to use?
FeedWordPress is a well-known plugin with 8,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 (2026.1030) and turn on automatic updates.
How do I find which version of FeedWordPress 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.