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

CVE-2026-12923

HIGH · 7.5 CVSS v3.1 Published 2026-07-01
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 7 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 Youtube Showcase plugin for WordPress is vulnerable to Arbitrary Function Call in versions up to and including 4.0.3. This is due to insufficient validation of the 'path' parameter in the emd_delete_file() AJAX handler in includes/common-functions.php. The user-supplied value is passed through sanitize_text_field(), has its trailing '_PLUGIN_DIR' substring stripped, and is then invoked as a PHP function name with no arguments via `$sess_name()`. The handler is gated only by a nonce — no current_user_can() check is present — and the nonce is emitted on any front-end page that renders a form shortcode containing file fields. This makes it possible for authenticated attackers, with Subscriber-level access and above, to invoke arbitrary zero-argument PHP functions (such as phpinfo, phpversion, get_defined_vars, error_get_last), resulting in sensitive information disclosure and potential further compromise depending on the functions available in the environment.

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 Youtube Showcase WordPress plugin versions up to 4.0.3 contain an Arbitrary Function Call vulnerability in the emd_delete_file() AJAX handler. The 'path' parameter, after sanitization and stripping of '_PLUGIN_DIR', is directly invoked as a PHP function via `$sess_name()`. The handler lacks a current_user_can() check and relies only on a nonce that is exposed on frontend forms, allowing any authenticated user with Subscriber-level access to call zero-argument PHP functions like phpinfo() or get_defined_vars().

MitigationAdd a current_user_can() capability check to the AJAX handler and implement a whitelist of allowed function names before invoking them to prevent arbitrary function execution.

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. Identify plugin installation and version
    Navigate to Plugins > Installed Plugins in WordPress admin, locate 'Youtube Showcase' or 'Youtube Embed Plus' plugin, and note the version number. Compare against affected range: versions up to and including 4.0.3.
    Affected if The plugin is installed and the version is 4.0.3 or lower.
  2. Confirm plugin is active
    Check the WordPress admin Plugins page to see if Youtube Showcase is currently activated.
    Affected if The plugin is active and version 4.0.3 or lower.
  3. Locate vulnerable AJAX handler
    Inspect plugin files via FTP or file manager. Navigate to /wp-content/plugins/youtube-showcase/ or similar path. Search for 'emd_delete_file' function and verify the code directly invokes the path parameter as a function (e.g., $sess_name()).
    Affected if The emd_delete_file() function exists and contains direct function call using unsanitized input.
  4. Check AJAX handler accessibility
    Examine the AJAX hook registration for wp_ajax_emd_delete_file and wp_ajax_nopriv_emd_delete_file. Verify if the handler lacks a current_user_can() capability check.
    Affected if The AJAX endpoint is registered without capability checks, allowing any authenticated user (Subscriber role or higher) to access it.

The environment is affected if the Youtube Showcase plugin version 4.0.3 or lower is installed and active, exposing an unauthenticated AJAX endpoint that allows arbitrary PHP function execution via the path parameter.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add a current_user_can() capability check to the AJAX handler and implement a whitelist of allowed function names before invoking them to prevent arbitrary function execution.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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