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

CVE-2026-15552

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 5 weeks old

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
Enterprise Cloud Database developed by Ragic has a Stored Cross-Site Scripting vulnerability, allowing unauthenticated remote attackers to inject persistent JavaScript code executed in users' browsers upon page load.

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

Ragic Enterprise Cloud Database contains a stored Cross-Site Scripting (XSS) vulnerability where unauthenticated remote attackers can inject persistent malicious JavaScript code into the database. This payload executes in users' browsers when they view the affected page, allowing session hijacking, credential theft, or defacement.

MitigationImplement contextual output encoding and input validation on all user-supplied data fields, apply Content Security Policy headers to restrict script execution, and conduct a thorough audit to identify all injection points across the application.

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
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. Identify Ragic installation
    Check your application's build files, deployment documentation, or admin console for product name 'Ragic Enterprise Cloud Database'. Look for 'Ragic' branding in the UI or HTTP response headers.
    Affected if The system is not Ragic Enterprise Cloud Database, this CVE does not apply.
  2. Determine installed version
    Locate the version number through the admin panel (typically under Help > About or Settings > Version), check the deployment manifest, or query the application's API endpoint for version information if available.
    Affected if The installed version is unknown or falls within the affected range (compare your version to any official Ragic security advisories for CVE-2026-15552).
  3. Verify user input fields exist
    Review your database schema for user-created or customizable fields that accept freeform text input. Check the Forms/Sheets configuration in the Ragic admin console for fields that store data directly into the database.
    Affected if The database contains customizable fields that accept user-supplied text without documented sanitization, creating potential XSS injection points.
  4. Inspect for stored scripts
    Query your database tables for common XSS payloads (such as '<script>', 'javascript:', 'onerror=', 'onload=') in text fields. Use a database query: SELECT * FROM [tablename] WHERE [field] LIKE '%<script%' OR [field] LIKE '%javascript:%'.
    Affected if Database records contain unsanitized HTML or JavaScript code that would execute when rendered in a browser.
  5. Check Content Security Policy headers
    Inspect HTTP responses from your Ragic instance using browser dev tools (Network tab) or a command-line tool like curl -I [url]. Look for Content-Security-Policy or X-Content-Security-Policy headers.
    Affected if CSP headers are missing or overly permissive (e.g., allow 'unsafe-inline' or 'unsafe-eval'), which would enable stored XSS to execute.

You are affected if you run Ragic Enterprise Cloud Database, your version is within the affected range, and your database contains user-input fields without proper output encoding or CSP protection.

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

Implement contextual output encoding and input validation on all user-supplied data fields, apply Content Security Policy headers to restrict script execution, and conduct a thorough audit to identify all injection points across the application.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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