CVE-2026-57798
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 SaurabhSharma NewsPlus Shortcodes newsplus-shortcodes allows PHP Local File Inclusion.This issue affects NewsPlus Shortcodes: from n/a through <= 4.2.0.
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 confidenceLocal File Inclusion (LFI) vulnerability in the NewsPlus Shortcodes WordPress plugin allows attackers to include arbitrary local PHP files through improperly controlled filename parameters in include/require statements. This can lead to remote code execution if attackers can inject malicious code into accessible files on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Confirm NewsPlus Shortcodes plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'NewsPlus Shortcodes' in the list of installed pluginsAffected if The plugin appears in the installed plugins list
-
Check the installed version of NewsPlus ShortcodesIn the Plugins list, find NewsPlus Shortcodes and note the version number displayed under the plugin name. Compare this version against any known affected versions or the latest available versionAffected if The installed version is older than any patched version or if the specific vulnerable version is confirmed
-
Verify the plugin is activeIn WordPress admin > Plugins, check if NewsPlus Shortcodes shows as 'Active' rather than 'Inactive' or 'Network Active'Affected if The plugin is activated and running on the site
-
Inspect plugin file inclusion logicAccess the WordPress site files via FTP or file manager, navigate to wp-content/plugins/newsplus-shortcodes, and examine PHP files for include/require statements that use dynamic parameters (such as $_GET, $_POST, or unsanitized variables) without proper validationAffected if Dynamic file inclusion using unsanitized input is found in the plugin code
-
Check for accessible file inclusion endpointsReview the plugin to identify any publicly accessible PHP files that accept filename parameters via URL (GET) or form (POST) requestsAffected if The plugin exposes endpoints that accept file path parameters without validation
A user is affected if the NewsPlus Shortcodes plugin is installed, activated, and contains the vulnerable file inclusion logic that allows arbitrary local PHP file inclusion through improperly controlled parameters.
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 to a patched version of NewsPlus Shortcodes if available. If no patch exists, implement strict input validation on all file inclusion parameters and whitelist allowed file paths to prevent arbitrary file inclusion.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57798 — 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-2026-57798 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