dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-48869

HIGH · 7.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Unauthenticated Cross Site Scripting (XSS) in Enfold <= 7.1.4 versions.

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

Unauthenticated Cross-Site Scripting (XSS) vulnerability in the Enfold WordPress theme affecting versions 7.1.4 and below. An unauthenticated attacker can inject malicious JavaScript through unsanitized user inputs, potentially leading to session hijacking, credential theft, or malicious redirects.

MitigationUpgrade Enfold to a version newer than 7.1.4; until patched, implement WAF rules to filter XSS payloads and disable the affected input vector if possible.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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 if Enfold theme is installed
    Inspect the WordPress themes directory (wp-content/themes/) for an 'enfold' folder, or query the wp_options table for 'template' or 'stylesheet' values matching 'enfold'.
    Affected if The Enfold theme directory exists or is set as the active/theme in WordPress.
  2. Determine installed Enfold version
    Open wp-content/themes/enfold/style.css and locate the 'Version:' declaration in the file header comments, or check via WordPress admin under Appearance > Themes.
    Affected if The version reads 7.1.4 or any version number lower than 7.1.4.
  3. Confirm vulnerability scope
    Since this is an unauthenticated XSS through unsanitized user inputs, any publicly accessible input field handled by the theme (such as search parameters, form inputs, or query string variables) could be the attack vector.
    Affected if The installed version is 7.1.4 or below AND the theme handles user-supplied input on the frontend without sanitization.

A system is affected if the Enfold WordPress theme version is 7.1.4 or lower and the theme is active, as the vulnerability allows unauthenticated attackers to inject malicious JavaScript via unsanitized inputs.

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

Upgrade Enfold to a version newer than 7.1.4; until patched, implement WAF rules to filter XSS payloads and disable the affected input vector if possible.

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-2026-48869 — 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-48869 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