CVE-2025-55126

6.5 MEDIUM

📋 TL;DR

This stored XSS vulnerability allows attackers to inject malicious scripts into advertiser campaign names, which then execute when users view affected pages. The vulnerability affects users accessing advertiser-related pages on the platform. Attackers can steal session cookies, redirect users, or perform actions on their behalf.

💻 Affected Systems

Products:
  • HackerOne platform
Versions: Unknown specific versions - vulnerability reported through HackerOne's bug bounty program
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the advertiser-related pages navigation box functionality. Requires attacker to have ability to create or modify campaign names.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator session cookies, gain full administrative access, compromise user accounts, and potentially pivot to internal systems.

🟠

Likely Case

Attackers steal user session cookies to hijack accounts, redirect users to phishing sites, or perform unauthorized actions within user contexts.

🟢

If Mitigated

With proper input validation and output encoding, malicious scripts are neutralized before execution, preventing any client-side impact.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires ability to create or modify campaign names. Stored XSS payloads execute automatically when users view affected pages.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown - fixed by HackerOne after report

Vendor Advisory: https://hackerone.com/reports/3411750

Restart Required: No

Instructions:

1. Apply HackerOne's security patch for the platform. 2. Ensure proper input validation and output encoding for campaign names. 3. Test that XSS payloads are properly sanitized.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement server-side validation to reject or sanitize HTML/JavaScript in campaign names

Content Security Policy

all

Implement strict CSP headers to prevent script execution from untrusted sources

🧯 If You Can't Patch

  • Implement WAF rules to block XSS payloads in campaign name parameters
  • Monitor for suspicious campaign name patterns and alert on potential XSS attempts

🔍 How to Verify

Check if Vulnerable:

Test by attempting to inject XSS payloads into campaign name fields and checking if they execute when viewing advertiser pages

Check Version:

Check HackerOne platform version or contact HackerOne support for patch verification

Verify Fix Applied:

Attempt to inject common XSS payloads into campaign names and verify they are properly sanitized and do not execute

📡 Detection & Monitoring

Log Indicators:

  • Unusual campaign name patterns containing script tags or JavaScript
  • Multiple failed attempts to create campaigns with special characters

Network Indicators:

  • Outbound connections to suspicious domains from advertiser pages
  • Unexpected POST requests with encoded payloads

SIEM Query:

search campaign_name=*script* OR campaign_name=*javascript* OR campaign_name=*onerror*

🔗 References

📤 Share & Export