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

CVE-2026-25356

HIGH · 7.1 CVSS v3.1 Published 2026-03-25
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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in skygroup Yobazar yobazar allows Reflected XSS.This issue affects Yobazar: from n/a through < 1.6.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

This is a reflected Cross-site Scripting (XSS) vulnerability in the Yobazar e-commerce platform. The application fails to properly sanitize user-supplied input before including it in web pages, allowing attackers to inject malicious JavaScript code that executes in victim browsers. This can lead to session hijacking, credential theft, or defacement.

MitigationUpgrade to Yobazar version 1.6.7 or later. Additionally, implement proper input validation and output encoding on all user-supplied data before rendering in HTML contexts, and consider deploying Content Security Policy (CSP) headers to mitigate XSS attacks.

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 Yobazar installation version
    Check for a version file in the application root directory, examine the admin dashboard for version information, or look for a version constant in the source code files
    Affected if Installed version is lower than 1.6.7 (versions prior to 1.6.7 are affected)
  2. Identify user input injection points
    Review the application's source code for endpoints that handle query parameters, form submissions, or URL segments and reflect them back in HTML responses without sanitization
    Affected if The application reflects user-supplied input (GET/POST parameters, URL paths) directly into page content without proper output encoding
  3. Locate vulnerable code handling request parameters
    Search source files for patterns where request parameters (like $_GET, $_POST, or similar) are concatenated directly into HTML output or echoed without escaping functions such as htmlspecialchars()
    Affected if Code is found that directly outputs request parameters into HTML without sanitization functions
  4. Verify absence of input validation
    Inspect the application's input handling logic to confirm no whitelist validation, sanitization, or output encoding is applied before reflecting user data into pages
    Affected if No input validation or output encoding is implemented for the vulnerable parameter handling

You are affected if your Yobazar installation version is below 1.6.7 and the application reflects unvalidated user input directly into web 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Yobazar version 1.6.7 or later. Additionally, implement proper input validation and output encoding on all user-supplied data before rendering in HTML contexts, and consider deploying Content Security Policy (CSP) headers to mitigate XSS attacks.

Recommended fix Moderate confidence

1.6.7

  1. 1. Backup your current Yobazar installation and database before proceeding with any updates.
  2. 2. Verify your current Yobazar version by checking the admin panel or version file.
  3. 3. Download Yobazar version 1.6.7 or later from the official vendor source.
  4. 4. Install the updated version following the standard vendor upgrade procedure.
  5. 5. After upgrade, verify the XSS vulnerability is resolved by testing input fields that could be vulnerable to reflected XSS.
  6. 6. Clear any application caches to ensure the new version is fully deployed.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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