dbcve.org
Frontend AdminWordPress extension · Dynamiapps

CVE-2025-26987

MEDIUM · 6.1 CVSS v3.1 Published 2025-02-25
Fix available
A fix is available. Upgrade to 3.25.18 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Shabti Kaplan Frontend Admin by DynamiApps acf-frontend-form-element allows Reflected XSS.This issue affects Frontend Admin by DynamiApps: from n/a through <= 3.25.17.

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

Reflected XSS vulnerability in the acf-frontend-form-element plugin (Frontend Admin by DynamiApps) allows attackers to inject malicious JavaScript through unsanitized input that gets rendered in web pages without proper encoding.

MitigationUpdate to a version newer than 3.25.17 when a patch becomes available. As a temporary measure, implement output encoding and input validation at the web application firewall level.

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.25.18

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Check plugin version in WordPress admin
    Navigate to Plugins > Installed Plugins in the WordPress admin dashboard. Locate 'Frontend Admin by DynamiApps' or 'acf-frontend-form-element' and note the version number displayed.
    Affected if The displayed version is below 3.25.18 (any version from the plugin's initial release up to 3.25.17).
  2. Check plugin version via filesystem
    If WordPress admin access is unavailable, access the server via FTP or file manager. Navigate to /wp-content/plugins/acf-frontend-form-element/ and locate the main plugin file (typically acf-frontend-form-element.php or similar). Open it and find the version definition in the plugin header comment.
    Affected if The version string found in the plugin file is lower than 3.25.18.
  3. Identify if plugin output functions handle user input
    Review plugin code in /wp-content/plugins/acf-frontend-form-element/ for instances where GET/POST parameters or user-submitted data are output to HTML without sanitization functions (such as esc_html(), esc_attr(), or wp_kses()). Look for echo or print statements that directly output request parameters.
    Affected if Code is found that outputs unsanitized user input, particularly in frontend-rendered contexts where the plugin displays form data or parameters.
  4. Verify plugin is active on public-facing pages
    Check if the plugin shortcode (commonly [acf_frontend_form] or similar) is used in published pages/posts, or if the plugin's frontend rendering is enabled in settings.
    Affected if The plugin is active and its shortcodes or frontend form features are in use on accessible web pages, allowing potential injection of malicious scripts through user-supplied input.

Your environment is affected if the installed Frontend Admin plugin version is below 3.25.18 and the plugin is actively rendering frontend forms or user-accessible pages.

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 3.25.18 or later
Fixed in 3.25.18
Interim mitigation

Update to a version newer than 3.25.17 when a patch becomes available. As a temporary measure, implement output encoding and input validation at the web application firewall level.

Recommended fix High confidence

3.25.18

  1. Update Frontend Admin plugin to version 3.25.18 or later
  2. Verify the update was successful by checking the plugin version in WordPress admin
  3. Test the application to confirm the XSS vulnerability is no longer present

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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