dbcve.org
Frontend AdminWordPress extension · Dynamiapps

CVE-2023-51411

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-29
Fix available
A fix is available. Upgrade to after 3.18.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Unrestricted Upload of File with Dangerous Type vulnerability in Shabti Kaplan Frontend Admin by DynamiApps.This issue affects Frontend Admin by DynamiApps: from n/a through 3.18.3.

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

Unrestricted file upload vulnerability in Frontend Admin WordPress plugin by DynamiApps allows authenticated attackers to upload dangerous file types (e.g., executable PHP scripts) without proper validation, potentially enabling remote code execution on the server.

MitigationUpgrade Frontend Admin plugin to version 3.18.4 or later which contains the security fix; alternatively, disable the plugin until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Frontend AdminWordPress extension
Affected:<= 3.18.3

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate Frontend Admin plugin installation
    Access WordPress admin panel, go to Plugins > Installed Plugins, and look for 'Frontend Admin' by DynamiApps. Alternatively, check the /wp-content/plugins/ directory for a folder named 'frontend-admin' or similar DynamiApps plugin folder.
    Affected if The plugin is installed and active on the WordPress site
  2. Identify installed plugin version
    In WordPress admin, click on the plugin name to view details and find the version number. Alternatively, open the main plugin PHP file (usually in wp-content/plugins/frontend-admin/) and look for the version comment in the file header, or check the readme.txt file.
    Affected if The displayed version is 3.18.3 or lower
  3. Determine if file upload feature is accessible
    Check if the site allows frontend file submissions or has frontend forms that accept file uploads. Look for any frontend submission pages, user profile upload fields, or post creation forms that may use Frontend Admin functionality.
    Affected if File upload forms or frontend submission features are publicly or author-level accessible
  4. Inspect uploads directory for suspicious files
    Check the /wp-content/uploads/ directory (and subdirectories by year/month) for newly created .php, .phtml, .phar, or other executable file types that were uploaded after the plugin installation or recent dates.
    Affected if Any PHP or executable files exist in the uploads directory, especially if they were uploaded recently or by low-privilege users
  5. Review user-uploaded content
    Check Media Library for any unexpected file uploads, and review any custom post types created via Frontend Admin that may contain malicious file references or scripts.
    Affected if Unexpected media files or posts with suspicious content appear in the system

The site is affected if Frontend Admin plugin version 3.18.3 or lower is installed AND the file upload functionality is accessible to authenticated users.

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
Upgrade available Upgrade to a release after 3.18.3
Interim mitigation

Upgrade Frontend Admin plugin to version 3.18.4 or later which contains the security fix; alternatively, disable the plugin until patched.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version higher than 3.18.3)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. 3. Locate 'Frontend Admin by DynamiApps' plugin
  4. 4. Check the current version number to confirm it is <= 3.18.3
  5. 5. Update the plugin to the latest available version from the WordPress plugin repository
  6. 6. Verify the update was successful by checking the installed version
  7. 7. Test file upload functionality if used on the site to ensure the fix does not break legitimate features

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

Fix this in Frontend Admin Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

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