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

CVE-2026-25304

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 Jaroti jaroti allows Reflected XSS.This issue affects Jaroti: from n/a through < 1.4.8.

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

A reflected Cross-site Scripting (XSS) vulnerability exists in the Jaroti web application (versions prior to 1.4.8). The application fails to properly sanitize user-supplied input before reflecting it back in web pages, allowing an attacker to inject malicious JavaScript code that executes in the victim's browser.

MitigationUpgrade Jaroti to version 1.4.8 or later to obtain the patch. Until then, implement input validation and output encoding on all user-controllable parameters.

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 Jaroti installation version
    Check the version number displayed in the application footer, admin panel, or in configuration files (such as version.php, config.php, or a VERSION file in the web root). Compare this version against the fixed version 1.4.8.
    Affected if The installed version is any version prior to 1.4.8 (e.g., 1.4.7, 1.4.6, 1.3.x, etc.)
  2. Locate user input entry points
    Identify all HTTP request parameters that the application accepts, including GET and POST parameters. Common entry points include search fields, login forms, URL query parameters, and contact forms.
    Affected if The application accepts any user-controllable input that gets reflected back in the HTTP response without validation.
  3. Test for reflected input in responses
    Submit a harmless test string (such as <script>alert(1)</script> or a unique identifier like TEST123) as a parameter value. Inspect the server response to see if this string appears unmodified or unescaped within the HTML response body.
    Affected if The submitted test string appears literally in the response HTML without being entity-encoded (e.g., appears as <script> rather than &lt;script&gt;)
  4. Verify output encoding implementation
    Examine the application source code or HTTP response headers. Check if the application uses output encoding functions (such as htmlspecialchars, htmlentities, or similar encoding functions) when reflecting user input back to the browser.
    Affected if User-supplied input is reflected in responses without proper HTML entity encoding or other output sanitization measures.

You are affected if the installed Jaroti version is prior to 1.4.8 AND the application reflects user-supplied input in web pages without sanitization or encoding.

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 Jaroti to version 1.4.8 or later to obtain the patch. Until then, implement input validation and output encoding on all user-controllable parameters.

Recommended fix Moderate confidence

1.4.8

  1. 1. Backup your current Jaroti installation before proceeding with any updates.
  2. 2. Download Jaroti version 1.4.8 from the official skygroup repository or distribution channel.
  3. 3. Replace the existing Jaroti files with the new version 1.4.8 files, preserving any custom configurations if required.
  4. 4. Verify that the application runs correctly after the upgrade.
  5. 5. Test the application to confirm the reflected XSS vulnerability is no longer present.
  6. 6. Monitor for any unexpected behavior or errors following the upgrade.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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