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

CVE-2026-36748

CRITICAL · 9.0 CVSS v3.1 Published 2026-06-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable

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
RockRMS v16.13 and before v.17.7.0 is vulnerable to Cross Site Scripting (XSS) via Social Media links in user profile.

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 · high confidence

RockRMS versions 16.13 and before 17.7.0 contain a stored Cross Site Scripting (XSS) vulnerability in the Social Media links field of user profiles. Attackers can inject malicious JavaScript that executes when other users view the compromised profile.

MitigationUpgrade to RockRMS v17.7.0 or later. Until then, implement output encoding when rendering social media links and consider disabling the social media link feature for untrusted users.

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

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

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. Locate the installed RockRMS version
    Access the RockRMS admin panel and navigate to Admin > Settings > About, or check the version file in the installation directory if accessible via file system. Compare the version number to the affected range (anything below 17.7.0).
    Affected if The installed version is any release prior to v17.7.0
  2. Confirm Social Media field exists in user profiles
    Navigate to Admin > Person > Person Detail Views (or equivalent profile configuration). Locate the Social Media or Connections section within the person profile template. Verify the field is present and enabled for user profile editing.
    Affected if The Social Media links field is present and available in user profile configuration
  3. Check user permissions for profile editing
    Go to Admin > Security > Permissions or Roles. Review what roles have permission to edit their own profile or other user profiles. Identify if standard users (non-admins) can modify profile fields including Social Media links.
    Affected if Non-administrative users have permission to edit profile fields containing Social Media links
  4. Inspect profile display for output encoding
    View a user profile on the front-end as a regular visitor. Inspect the page source or use browser developer tools to examine how Social Media link values are rendered. Look for unescaped HTML/JavaScript in the href or display text areas.
    Affected if Social Media field values are rendered without HTML encoding (raw output of user-supplied data)

You are affected if your RockRMS version is before 17.7.0 AND the Social Media links field is accessible to users who can inject unencoded content that displays to other users.

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 RockRMS v17.7.0 or later. Until then, implement output encoding when rendering social media links and consider disabling the social media link feature for untrusted users.

Recommended fix Moderate confidence

RockRMS v17.7.0 or later

  1. 1. Back up the current RockRMS database and configuration files before making any changes.
  2. 2. Navigate to the RockRMS administration panel.
  3. 3. Locate the Social Media links section in user profile settings.
  4. 4. Upgrade RockRMS to version 17.7.0 or later by downloading the latest release from the official RockRMS repository.
  5. 5. Apply the upgrade following the standard RockRMS upgrade documentation.
  6. 6. Verify the Social Media link input fields now properly sanitize user input.
  7. 7. Test by attempting to inject script tags in Social Media link fields to confirm XSS is mitigated.
  8. 8. Monitor for any unexpected behavior after the upgrade.
Caveat Review release notes for v17.7.0 for any database schema changes or configuration updates that may require adjustment

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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