dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-49303

MEDIUM · 6.8 CVSS v3.1 Published 2025-07-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Shabti Kaplan Frontend Admin by DynamiApps acf-frontend-form-element allows Path Traversal.This issue affects Frontend Admin by DynamiApps: from n/a through <= 3.28.7.

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

Path traversal vulnerability in acf-frontend-form-element (Frontend Admin by DynamiApps) plugin allows attackers to access files outside the restricted directory through manipulation of file paths using '../' sequences. This is a medium-severity (CVSS 6.8) issue affecting versions up to and including 3.28.7.

MitigationUpdate to the latest patched version of the plugin when released. In the interim, implement server-side input validation to sanitize file path references and restrict file system permissions.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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. Locate the acf-frontend-form-element plugin installation
    Check your WordPress wp-content/plugins directory for the acf-frontend-form-element or frontend-admin folder. Identify the main plugin file (usually main.php or the primary PHP file) to find version information.
    Affected if The plugin folder exists in the WordPress plugins directory.
  2. Determine the installed plugin version
    Open the main plugin PHP file and look for a version constant or header comment (typically contains 'Version: x.x.x' or a 'Version' define). Compare this version number to the affected range (versions up to and including 3.28.7).
    Affected if The installed version is 3.28.7 or lower.
  3. Verify if file upload or file handling features are enabled
    Check the plugin settings in the WordPress admin panel under the Frontend Admin or acf-frontend-form-element settings. Look for configurations related to file uploads, file management, or any feature that processes file paths.
    Affected if File upload, file picker, or file management functionality is enabled and accessible to users.
  4. Inspect server configuration for public access to plugin endpoints
    Review your web server logs and access patterns for requests to plugin files that handle file operations. Check if any AJAX endpoints or public-facing forms in the plugin are accessible without authentication.
    Affected if Unauthenticated or low-privilege users can access file-handling endpoints provided by this plugin.

You are affected if the plugin is installed with version 3.28.7 or lower AND file-handling features are enabled and accessible to potentially malicious 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest patched version of the plugin when released. In the interim, implement server-side input validation to sanitize file path references and restrict file system permissions.

Recommended fix Moderate confidence

Latest version of Frontend Admin by DynamiApps (acf-frontend-form-element) newer than 3.28.7

  1. Check the WordPress admin panel or the plugin repository for the latest version of 'Frontend Admin by DynamiApps' (acf-frontend-form-element)
  2. Upgrade the plugin to the latest available version (ensure it is newer than version 3.28.7)
  3. Verify the upgrade was successful by checking the installed version number
  4. Test the file upload functionality if applicable to ensure the path traversal is mitigated
  5. Review any changelog or security release notes for the new version
Caveat Review plugin changelog for any breaking changes between your current version and the new version before upgrading in production

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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