dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-11426

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

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 UnderConstructionPage PRO plugin for WordPress is vulnerable to Arbitrary File Read in all versions up to, and including, 5.76. This is due to the plugin accepting arbitrary local file paths in the template_thumbnail parameter and copying their contents into a publicly accessible uploads file. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read arbitrary files on the server, which can 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 · moderate confidence

The UnderConstructionPage PRO WordPress plugin versions up to 5.76 contains an arbitrary file read vulnerability. Authenticated attackers with Subscriber-level access can supply arbitrary local file paths via the template_thumbnail parameter, which the plugin copies to a publicly accessible uploads directory, exposing server file contents.

MitigationUpdate the plugin to a version beyond 5.76 when available, or implement strict input validation on the template_thumbnail parameter to restrict file path access and prevent path traversal.

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Verify the UnderConstructionPage PRO plugin is installed
    In the WordPress admin dashboard, navigate to Plugins > Installed Plugins and look for 'UnderConstructionPage PRO' or 'under-construction-page-pro' in the plugin list. Alternatively, check the /wp-content/plugins/ directory for a folder named under-construction-page-pro or similar.
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In the plugins list, click on the plugin to view details, or check the main plugin PHP file header for the 'Version' tag. You can also examine the plugin's main PHP file in /wp-content/plugins/[plugin-folder]/
    Affected if The version number is 5.76 or lower
  3. Confirm subscriber-level accounts exist
    In WordPress admin, go to Users > All Users and review user roles. Subscriber is the lowest privilege level in WordPress.
    Affected if Any user account with the Subscriber role exists on the site
  4. Check if the plugin's template thumbnail functionality is exposed
    Review the plugin's settings pages for any option that accepts a template_thumbnail parameter or file path input for construction page templates. This may be visible in the plugin's template selection or upload feature.
    Affected if The plugin allows uploading or selecting thumbnail images for templates without admin-level access restrictions
  5. Inspect the uploads directory for unexpected files
    Check /wp-content/uploads/ and subdirectories for any files that were created recently or contain unexpected names that may have been copied from system paths like /etc/passwd or other local files.
    Affected if Files in the uploads directory contain content from server system files or appear to be copies of files outside the intended upload scope

A user is affected if the UnderConstructionPage PRO plugin version is 5.76 or lower AND at least one Subscriber-level account exists and the vulnerable template_thumbnail parameter is accessible to that role.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version beyond 5.76 when available, or implement strict input validation on the template_thumbnail parameter to restrict file path access and prevent path traversal.

Recommended fix Moderate confidence

Upgrade to UnderConstructionPage PRO version 5.77 or later (the latest available version)

  1. 1. Log in to the WordPress admin dashboard with an administrator account.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the UnderConstructionPage PRO plugin in the list.
  4. 4. If an update is available, click the 'Update Now' link next to the plugin.
  5. 5. Wait for the update to complete and verify the plugin is now at version 5.77 or higher.
  6. 6. Test that the plugin functionality works as expected after the update.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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