CVE-2026-57789
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 jwsthemes Aqua aqua allows PHP Local File Inclusion.This issue affects Aqua: from n/a through <= 5.1.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 · high confidenceLocal File Inclusion (LFI) vulnerability in the jwsthemes Aqua WordPress theme (versions up to 5.1.2) allows attackers to manipulate include/require statements to execute arbitrary local PHP files due to improper validation of user-supplied file path parameters.
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 Aqua theme is installedCheck for the Aqua theme directory in your WordPress installation at wp-content/themes/aqua/ or list all installed themes via WordPress admin under Appearance > ThemesAffected if The Aqua theme directory exists in wp-content/themes/
-
Identify the installed theme versionOpen the theme's style.css file (wp-content/themes/aqua/style.css) and locate the 'Version:' header in the comment block at the top, or check the theme version displayed in WordPress admin under Appearance > ThemesAffected if The version number is 5.1.2 or lower, or if no version is displayed and the theme appears to be the Aqua theme by jwsthemes
-
Determine if the theme is activeIn WordPress admin, go to Appearance > Themes and check if the Aqua theme is currently activated; or query the wp_options table for the 'template' or 'stylesheet' option valuesAffected if Aqua is the active/current theme being used on the site
-
Locate vulnerable file inclusion codeSearch the theme files (particularly PHP files in the theme root and includes subdirectories) for patterns like include($_GET[, require($_GET[, include($_REQUEST[, or similar where user-supplied parameters are used directly in file inclusion functions without validationAffected if Any PHP files in the theme contain include/require statements that use $_GET, $_POST, or $_REQUEST variables directly without sanitization or validation checks
-
Test for LFI parameter exposureIdentify any URL parameters used in file inclusion (commonly named 'file', 'path', 'page', 'include', or similar) and check if the theme routes requests through these parameters; review the theme's PHP files to trace how these parameters are processedAffected if URL parameters related to file paths are accepted by the theme and used in include/require statements without proper validation
You are affected if the Aqua theme versions 5.1.2 or lower is installed, the theme is active, and the theme code contains include/require statements that use unsanitized user-supplied input for file paths.
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 Aqua theme to the latest patched version. If immediate patching is unavailable, disable the theme and implement input validation on file inclusion parameters, ensuring PHP's allow_url_include is disabled.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57789 — 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-57789 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