Easy Digital DownloadsWordPress extension · Wow Company
CVE-2024-35629
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Wow-Company Easy Digital Downloads – Recent Purchases allows PHP Remote File Inclusion.This issue affects Easy Digital Downloads – Recent Purchases: from n/a through 1.0.2.
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 · moderate confidenceA Remote File Inclusion (RFI) vulnerability in the Wow-Company Easy Digital Downloads – Recent Purchases WordPress plugin (versions up to 1.0.2) allows attackers to include arbitrary remote PHP files via improper control of filenames in include/require statements, potentially leading to full server compromise through arbitrary code execution.
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
Easy Digital DownloadsWordPress extension
<= 1.0.2CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check if Wow Company Easy Digital Downloads plugin is installedNavigate to WordPress Admin > Plugins > Installed Plugins and look for 'Easy Digital Downloads - Recent Purchases' by Wow Company, or check the file system at wp-content/plugins/ for a folder containing 'wow-company' or 'easy-digital-downloads-recent-purchases'Affected if The plugin is present in the plugins directory regardless of version
-
Determine the installed plugin versionIn WordPress Admin, click on the plugin to view details and read the version number, or open the main plugin PHP file (usually plugin-name.php) and look for the 'Version' header in the plugin commentsAffected if Version is 1.0.2 or lower
-
Verify if the plugin is activeIn WordPress Admin > Plugins, check if the plugin has an 'Active' status under the plugin nameAffected if The plugin is currently activated on the site
-
Inspect plugin files for include/require statements with user-controlled inputExamine PHP files in the plugin directory for dynamic include/require statements that use variables from $_GET, $_POST, or other request parameters without proper sanitizationAffected if Vulnerable include/require patterns are found that accept external input
-
Check web server logs for suspicious include/require requestsReview access logs for requests to the plugin's PHP files containing URLs or file paths in query parameters (e.g., ?file=http://attacker.com/malicious.php)Affected if Suspicious RFI patterns are found in logs targeting the plugin
A site is affected if the Wow Company Easy Digital Downloads - Recent Purchases plugin version 1.0.2 or lower is installed and active on the WordPress instance.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the plugin to the latest version immediately. If no patched version is available, disable or remove the plugin entirely and review server configuration for protection against remote file inclusion attempts.
Fix this in Easy Digital Downloads
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35629 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-35629 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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