NewscardWordPress extension · Themehorse
CVE-2024-50434
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 themehorse NewsCard newscard.This issue affects NewsCard: from n/a through <= 1.3.
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 confidenceThis is a Remote File Inclusion (RFI) vulnerability in the themehorse NewsCard plugin. The vulnerability allows attackers to include remote files via improper control of filename parameters in PHP include/require statements, potentially leading to 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
NewscardWordPress extension
< 1.4CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify if Newscard theme is installedCheck the WordPress themes directory (wp-content/themes/) for a folder named 'newscard', 'newscard-theme', or similar themehorse naming. List all installed themes and look for the Newscard theme.Affected if The Newscard theme by themehorse is found in the themes directory
-
Check the installed Newscard versionOpen the theme's style.css file in the newscard theme folder and look for the 'Version:' header in the CSS comment block at the top. Alternatively, check version in functions.php.Affected if The version is listed as 1.3 or lower, or if no version is found but the theme is present and was downloaded before the patch
-
Locate the vulnerable include/require codeSearch the theme's PHP files (especially functions.php, header.php, footer.php, or any file handling template includes) for include(), include_once(), require(), or require_once() statements where a parameter appears to accept user input or is constructed dynamically.Affected if PHP include/require statements are found that use variables in the file path without proper sanitization, allowing external control of the filename parameter
-
Verify the attack surface is accessibleExamine if the vulnerable include/require is triggered through a URL parameter (common in WordPress: ?page= or custom parameters). Check if the parameter can be manipulated via HTTP requests to inject a remote URL.Affected if The vulnerable code accepts input from $_GET, $_POST, or $_REQUEST superglobals and uses it directly in include/require without validation
A user is affected if the Newscard theme by themehorse is installed at version 1.3 or below AND the vulnerable PHP include/require code that allows user-controlled filenames is present and accessible via web requests.
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.
dbcve · scoped1.4
Replace dynamic file inclusion with static includes, implement allowlist validation for included files, and remove or properly sanitize any user-controllable input used in include/require paths.
Newscard version 1.4
- 1. Backup your current WordPress site and database before making any changes
- 2. Update the NewsCard theme to version 1.4 or later through the WordPress dashboard (Appearance > Themes) or via wp-cli: wp theme update newscard
- 3. Verify the update was successful by checking the theme version in WordPress admin under Appearance > Themes
- 4. Test critical site functionality to ensure the theme update did not break any customizations
- 5. If using any child themes, verify compatibility with the new parent theme version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Newscard
Scoped from the published advisory
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50434 — 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-50434 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