# CVE-2024-1317: RSS Aggregator by Feedzy <= 4.4.2 - Authenticated(Contributor+) SQL Injection

> Authenticated contributors can exploit SQL injection in the Feedzy plugin to extract sensitive database information.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-4xx5-qm5g-p5ph

## What is CVE-2024-1317?

CVE-2024-1317 is a high-severity SQL injection vulnerability in themeisle RSS Aggregator by Feedzy – Feed to Post, Autoblogging, News & YouTube Video Feeds Aggregator, published on 20 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The RSS Aggregator by Feedzy – Feed to Post, Autoblogging, News & YouTube Video Feeds Aggregator plugin for WordPress is vulnerable to SQL Injection via the ‘search_key’ parameter in all versions up to, and including, 4.4.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query.  This makes it possible for authenticated attackers, with contributor access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-1317?

It affects 1 product.


Products: Themeisle Rss Aggregator by Feedzy.

## How do I fix CVE-2024-1317?

No fix has been published for CVE-2024-1317 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-1317 being exploited?

There is no known exploitation of CVE-2024-1317 in the wild and no public exploit code.

## Other vulnerabilities in themeisle RSS Aggregator by Feedzy – Feed to Post, Autoblogging, News & YouTube Video Feeds Aggregator

- [CVE-2024-1318](https://insights.sbomify.com/CVE-2024-1318/): RSS Aggregator by Feedzy <= 4.4.2 - Missing Authorization to Arbitrary Page Creation and Publication (medium 6.5)
- [CVE-2023-6805](https://insights.sbomify.com/CVE-2023-6805/): Server-side request forgery in RSS Aggregator by Feedzy – Feed to Post, Autoblogging, News & YouTube Video Feeds Aggregator (medium 6.4)
- [CVE-2023-6877](https://insights.sbomify.com/CVE-2023-6877/): Cross-site scripting in RSS Aggregator by Feedzy – Feed to Post, Autoblogging, News & YouTube Video Feeds Aggregator (medium 6.4)
- [CVE-2023-6801](https://insights.sbomify.com/CVE-2023-6801/): Cross-site scripting in RSS Aggregator by Feedzy – Feed to Post, Autoblogging, News & YouTube Video Feeds Aggregator (medium 6.4)
- [CVE-2023-6798](https://insights.sbomify.com/CVE-2023-6798/): Missing authorization in RSS Aggregator by Feedzy – Feed to Post, Autoblogging, News & YouTube Video Feeds Aggregator (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1317 and fix it if it is affected.

What it is: CVE-2024-1317 is a high-severity SQL injection vulnerability in themeisle RSS Aggregator by Feedzy – Feed to Post, Autoblogging, News & YouTube Video Feeds Aggregator, published on 20 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1317 in the wild and no public exploit code.

Affected product: themeisle RSS Aggregator by Feedzy – Feed to Post, Autoblogging, News & YouTube Video Feeds Aggregator. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-1317/ (Markdown: https://insights.sbomify.com/CVE-2024-1317/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-1317
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-1317
- OSV: https://osv.dev/vulnerability/CVE-2024-1317

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-1317/
Summaries are generated and may contain mistakes; the official description above is the record.