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

CVE-2026-34241

HIGH · 8.7 CVSS v3.1 Published 2026-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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
CtrlPanel is open-source billing software for hosting providers. Versions 1.1.1 and prior contain a Stored Cross-Site Scripting (XSS) vulnerability in the ticket reply notification system. Unsanitized reply content ($newmessage) is stored directly in database notification payloads and later rendered unescaped via Blade's {!! !!} syntax in the recipient's browser. The flaw exists in both App\Notifications\Ticket\Admin\AdminReplyNotification (triggered when a user replies, targeting admins) and App\Notifications\Ticket\User\ReplyNotification (triggered when an admin replies, targeting users), allowing arbitrary JavaScript execution in the victim's session context. A low-privileged attacker can exploit this to hijack admin sessions, harvest credentials via fake login prompts or keyloggers, and escalate privileges by performing administrative actions on the victim's behalf. The reverse path also enables a malicious or compromised admin to target regular users in the same manner. This issue has been fixed in version 1.2.0.

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

CtrlPanel versions 1.1.1 and prior contain a stored XSS vulnerability in the ticket reply notification system. Unsanitized reply content is stored directly in the database and rendered unescaped via Blade's {!! !!} syntax, allowing arbitrary JavaScript execution in the victim's browser. The flaw affects both AdminReplyNotification (user replies to admins) and ReplyNotification (admin replies to users).

MitigationUpgrade to CtrlPanel version 1.2.0 which contains the fix. Alternatively, implement input sanitization on $newmessage before database storage and/or change Blade's {!! !!} to {{ !! }} syntax for escaped output.

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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/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. Check installed CtrlPanel version
    Locate the version file or composer.json in the CtrlPanel installation directory and read the version number
    Affected if Version is 1.1.1 or prior (any version up to and including 1.1.1)
  2. Identify affected notification classes
    Search for AdminReplyNotification.php and ReplyNotification.php in the application codebase, typically under app/Notifications/
    Affected if Both notification classes exist in the installation
  3. Examine notification blade templates for unsafe rendering
    Find the blade template files associated with AdminReplyNotification and ReplyNotification (usually in resources/views/emails/ or resources/views/notifications/) and inspect them for {!! $newmessage !!} or {!! $message !!} syntax
    Affected if Templates contain {!! !!} syntax wrapping reply content variables like $newmessage or $message
  4. Verify database notification payload handling
    Inspect the notification classes for direct storage of unsanitized reply content in the toArray() or toDatabase() methods
    Affected if Reply content is stored without sanitization/escaping in notification data arrays

A user is affected if they are running CtrlPanel version 1.1.1 or prior AND the notification templates use {!! !!} syntax to render reply content without escaping.

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 CtrlPanel version 1.2.0 which contains the fix. Alternatively, implement input sanitization on $newmessage before database storage and/or change Blade's {!! !!} to {{ !! }} syntax for escaped output.

Recommended fix High confidence

1.2.0

  1. 1. Create a complete backup of the current CtrlPanel installation and database
  2. 2. Download CtrlPanel version 1.2.0 or later from the official repository
  3. 3. Replace the existing installation files with the new version
  4. 4. Run any provided migration scripts or database updates if included in the release
  5. 5. Verify the upgrade was successful by logging into the application
  6. 6. Test the ticket reply notification system by sending a test reply containing HTML/script tags to confirm content is properly escaped
  7. 7. Clear any application caches to ensure the new code is active
Caveat Review the 1.2.0 release notes for any breaking changes before upgrading, particularly if using custom notifications or themes

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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