VulnTitan VulnTitan Security command center
Plugin Vulnerability Hub
Plugin 1 known issue Latest disclosed Oct 04, 2007

feedburner-feedsmith Vulnerabilities

Review known vulnerability records for the WordPress plugin feedburner-feedsmith (`feedburner-feedsmith`), including severity, CVE references, affected versions, and patch status.

Recent tracked CVEs on this page include CVE-2007-5229, so operators can jump from disclosure to patch validation without scanning the full feed first.

View on WordPress.org Back to Feed
Known Records
1
High or Critical
1
Patch Coverage
100%
Last Updated
Jan 22, 2024
Related Security Guides

Use these guides while reviewing feedburner-feedsmith fixes

Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.

Hardening
WordPress hardening checklist for exposed plugins

Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Plugin Security
WordPress plugin security basics for patch decisions

Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Scanning
WordPress vulnerability scanner buyer's guide

Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Patch Decision Workflow

How to prioritize feedburner-feedsmith remediation

Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.

Search-Ready Records
1
1. Match the Package
Confirm the installed WordPress plugin slug is feedburner-feedsmith before acting on any CVE from this cluster.
2. Sort by Severity
Start with 1 high or critical record, then review medium and unrated findings with public references.
3. Check Patch Evidence
1 record include a patch path; verify compatibility before closing the finding.
4. Monitor Gaps
0 records still lack a listed fixed release, so keep this hub in the review queue.
High-Signal Remediation Targets
CVE-2007-5229 High
Cross-Site Request Forgery remediation for feedburner-feedsmith

Affected range: Versions up to 2.2. Fixed version: 2.3.

Priority CVE Quick Links

Fast paths into feedburner-feedsmith CVE reports

Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.

Indexed CVEs
1
Tracked CVE Issue Type Affected Versions Fixed Version CVSS
CVE-2007-5229
FeedBurner FeedSmith <= 2.2 - Cross-Site Request Forgery
 Cross-Site Request Forgery Versions up to 2.2 2.3 CVSS 8.8
CVE-2007-5229 High 2.3
CVE-2007-5229 feedburner-feedsmith Cross-Site Request Forgery

FeedBurner FeedSmith <= 2.2 - Cross-Site Request Forgery

Coverage Snapshot

What this page helps you verify fast

This hub clusters tracked records for feedburner-feedsmith so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.

Patch Visibility
1 record include a published patch path, leaving 0 with no listed safe release yet.
Severity Mix
0 critical and 1 high severity finding.
Recent CVEs
CVE-2007-5229
Reference Workflow
Jump from the hub into the full report when you need remediation notes, exploit context, CVSS vectors, or source references.
Triage First

Open the records most likely to drive action

These recent records surface the CVE strings, patch cues, and direct report links most operators need first.

Known Vulnerabilities

Reports for feedburner-feedsmith

Sorted by latest disclosure date so newly published issues surface first.

Plugin High Patched: Yes CVE-2007-5229
CVE-2007-5229: FeedBurner FeedSmith <= 2.2 - Cross-Site Request Forgery

Cross-site request forgery (CSRF) vulnerability in the FeedBurner FeedSmith 2.2 plugin for WordPress allows remote attackers to change settings and hijack blog feeds via a request to wp-admin/options-general.php that submits parameter values to FeedBurner_FeedSmith_Plugin.php, as...

Published
Oct 04, 2007
Patched Release
2.3
Affected Versions
Versions up to 2.2
Next Step
Update to 2.3 or newer if supported.
Review CVE-2007-5229 fixed version details Open CVE Reference