dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2026-1257

HIGH · 7.5 CVSS v3.1 Published 2026-01-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

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 Administrative Shortcodes plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 0.3.4 via the 'slug' attribute of the 'get_template' shortcode. This is due to insufficient path validation on user-supplied input passed to the get_template_part() function. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other "safe" file types can be uploaded and included.

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 confidence

The Administrative Shortcodes WordPress plugin versions up to 0.3.4 contains a Local File Inclusion vulnerability via the 'slug' parameter in the 'get_template' shortcode. Insufficient path validation in the get_template_part() call allows authenticated users with Contributor-level access or higher to include and execute arbitrary files on the server, leading to potential code execution.

MitigationUpdate the Administrative Shortcodes plugin to the latest patched version. If unable to update immediately, disable the get_template shortcode or restrict contributor-level access until a patch is applied.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Administrative Shortcodes plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and search for 'Administrative Shortcodes', or inspect the plugin directory /wp-content/plugins/ for an administrative-shortcodes folder
    Affected if the plugin folder exists in the WordPress installation
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find Administrative Shortcodes, and note the version number displayed
    Affected if the version is 0.3.4 or lower (any version up to and including 0.3.4)
  3. Confirm users with Contributor-level or higher access exist
    In WordPress admin, navigate to Users and review the role column for each user account; Contributor, Author, Editor, and Administrator roles all meet the requirement
    Affected if at least one user account has Contributor, Author, Editor, or Administrator role AND the plugin version is vulnerable
  4. Verify the get_template shortcode is available
    The shortcode is active whenever the Administrative Shortcodes plugin is active; check the plugin file /wp-content/plugins/administrative-shortcodes/includes/ or similar to confirm the get_template shortcode handler exists
    Affected if the plugin is active and the get_template shortcode function is present in the codebase

A user is affected if the Administrative Shortcodes plugin version 0.3.4 or lower is installed, the plugin is active, and at least one user with Contributor-level or higher access exists in the WordPress site.

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 Administrative Shortcodes plugin to the latest patched version. If unable to update immediately, disable the get_template shortcode or restrict contributor-level access until a patch is applied.

Recommended fix Moderate confidence

Administrative Shortcodes version 0.3.5 or later

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins.
  3. 3. Locate the 'Administrative Shortcodes' plugin in the list.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/administrative-shortcodes/ and upload via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin version is greater than 0.3.4.
  7. 7. Ensure users with Contributor-level or higher roles do not have unnecessary permissions until the patch is applied.
Caveat No known breaking changes reported for this security update

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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