dbcve.org
FeedwordpressWordPress extension · Feedwordpress Project

CVE-2024-0839

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-13
Fix available
A fix is available. Upgrade to 2024.0428 or later.
See remediation →
62/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 FeedWordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2022.0222 due to missing validation on the user controlled 'guid' key. This makes it possible for unauthenticated attackers to view draft posts that may contain sensitive information.

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

The FeedWordPress WordPress plugin fails to validate authorization on the 'guid' parameter, allowing unauthenticated attackers to access draft posts via IDOR. Attackers can enumerate the guid parameter to view sensitive content in unpublished posts that were intended to remain private.

MitigationUpdate FeedWordPress to version 2022.0223 or later. Until a patch is available, restrict access to the wp-admin area and consider disabling the plugin if exposure of draft content is a concern.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FeedwordpressWordPress extension
Affected:< 2024.0428

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Confirm FeedWordPress plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins. Look for 'FeedWordPress' in the list of active plugins.
    Affected if FeedWordPress appears in the installed plugins list
  2. Check installed FeedWordPress version
    In WordPress admin, go to Plugins > Installed Plugins and locate FeedWordPress. The version number is displayed below the plugin name. Compare this to the affected range: versions prior to 2024.0428.
    Affected if Installed version is less than 2024.0428
  3. Verify draft posts exist in the system
    In WordPress admin, go to Posts > All Posts. Look for posts with 'Draft' status. The vulnerability allows access to unpublished draft content.
    Affected if There are draft posts present in the WordPress installation
  4. Test unauthenticated access to guid parameter
    With a non-authenticated browser session, attempt to access a URL pattern such as yoursite.com/?feedwordpress=1&guid=[number] where [number] is a post ID that corresponds to a draft post. Observe if draft content is displayed without login.
    Affected if Draft post content is displayed to unauthenticated users via the guid parameter

If FeedWordPress is installed with a version below 2024.0428 and draft posts exist in the system, the environment is likely affected by this IDOR 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
Upgrade available Upgrade to 2024.0428 or later
Fixed in 2024.0428
Interim mitigation

Update FeedWordPress to version 2022.0223 or later. Until a patch is available, restrict access to the wp-admin area and consider disabling the plugin if exposure of draft content is a concern.

Recommended fix High confidence

2024.0428 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the FeedWordPress plugin
  4. Click 'Update now' if an update is available, or manually update to version 2024.0428 or later
  5. Verify the update completed successfully by checking the plugin version

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

Fix this in Feedwordpress Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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