Snapshot 165308

Document
Security advisories
URL
https://www.sprinklr.com/responsible-disclosure/
Fetched
HTTP status
200
Content type
text/html
Fetch mode
static
Size
488921 bytes
SHA-256 (raw)
0fdfdd616713ce96a7ea7a383bbef1f9e0a6be2137b0b61a47717ff42ea92e44
SHA-256 (normalized text)
b81632720cdef852e4bbcb341c0a6a92b2024203db8e30a0e5c6e16139aeeef1

Normalized text

Scripts and page chrome removed; this is what change detection compares.

Login
Support
Sprinklr
Product Suites
Platform
Sprinklr Service
Overview
Inbound Contact Center
Outbound Contact Center
Social Customer Service
Live Chat Support
Sprinklr VoiceConnect
Omnichannel Routing
Unified Agent Desktop
Supervisor Console
Conversational IVR
Workforce Management
Community Software
AI Agent Platform
Agent Copilot
Quality Management
Conversational Analytics
Knowledge Base Platform
Guided Workflows
Omnichannel Surveys
Reporting and Analytics
Service Command Center
Sprinklr Social
Overview
Social Publishing and Engagement
Social Marketing for Distributed Teams
Employee Advocacy
Works Best With
Social Listening
Social Advertising
Social Customer Service
Sprinklr Insights
Overview
Social Listening
Competitive Insights and Benchmarking
Product Insights
Location Insights
Visual Insights
Sprinklr Surveys
LLM Insights
Video Intelligence
Sprinklr Marketing
Overview
Content Marketing and Campaign Planning
Social Advertising
Unified Analytics
Ad Comment Moderation
Unified-CXM
Overview
Integrations
Sandbox
Security
APIs
Active Data Retention
Display
Presentations
SPOTLIGHT
Sprinklr named a Leader in The Forrester Wave™: Social Suites, Q4 2024
Read full report
Sprinklr named a Strong Performer in The Forrester Wave™: CCaaS Platforms, Q2 2025
Read full report
CPG
Financial Services
Government
Retail
Technology
Telecommunications
Travel & Hospitality
Marketing Teams
Overview
Marketing AI Agents
Content Lifecycle Management
Social Media Management
Social Advertising
Customer Service Teams
Overview
Omnichannel Contact Center
Customer Self-Service
Digital Customer Service
Outbound Campaign Management
Contact Center Intelligence
CX Teams
Overview
Customer Feedback Management
Contact Center Intelligence
SPOTLIGHT
Aramex delivers world-class CX with AI-powered CCaaS and 24/7 customer care
Read full story
Acer streamlines workflows across global markets and transforms the customer experience
Read full story
Overview
Sprinklr AI Agents
Sprinklr Copilot
AI+ Studio
SPOTLIGHT
Check your AI maturity in minutes and get a free report with strategies to improve your AI readiness
Get started
Northwestern Mutual uses Sprinklr AI to power its most successful social campaign ever
Read full story
Customer Stories
Sprinklr Champions
Sprinklr Community
CXUnifier Awards
SPOTLIGHT
Uber achieves industry-leading SLA and response times
Read full story
Deutsche Telekom rings in the future of CX with AI-powered CCaaS
Read full story
Our Story
Leadership
Newsroom
Partners
Careers
Investor Relations
Security & Data Privacy
Sustainability
SPOTLIGHT
Sprinklr wins Cloud-Based CX Solution of the Year at the 2025 CCW Excellence Awards
Learn more
Join a culture where kindness and customer obsession defines everything we do
Learn more
AI Maturity Assessment
CX-WISE
CX Connect
Analyst Reports
Forbes Influential CMOs 2026
Sprinklr Demo Center
eBooks & Reports
Events & Webinars
Blog
Videos
Our Services
Training
For Agencies
Help Center
Release Notes
Contact Us
Latest release
Overview
Release Webinars
Release library
Summer '26
Spring '26
Winter'26
SPOTLIGHT
Aramex delivers world-class CX with AI-powered CCaaS and 24/7 customer care
Read full story
Acer streamlines workflows across global markets and transforms the customer experience
Read full story
Sprinklr’s Vulnerability Disclosure Program
The Submission Process
If you believe you have found a vulnerability, immediately create a submission through our Hackerone platform. You can submit a bug through hackerone.
You will be recognized for your efforts if you were the first to report a valid vulnerability as per the rules of the vulnerability disclosure program.
Guidelines for Responsible Disclosure
Security research should be performed within the scope defined below:
While performing the research there should not be any disruption of systems, privacy violations and degradation to user experience.
The identified communication channels are the “submit” URL link or the “submission form” for submitting a vulnerability.
DO NOT report a security vulnerability to any other Sprinklr’s partner, client, employee and email.
Security vulnerability found in Sprinklr’s APIs utilized on our partner and customer website also fall under this responsible disclosure program.
DDoS attacks DO NOT qualify under this program and website should not be tested against such attacks.
Information about the vulnerability should not be disclosed publicly.
Information about finding a vulnerability also should not be disclosed publicly.
The researcher should not put the screenshots, videos, screen grabs or any other sensitive information regarding the vulnerability on any external websites like Imgur, Vimeo, YouTube, Dropbox, etc.
Violation of the stated policy (both general guidelines and program policy) can result in enforcement of necessary legal actions.
When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
Clickjacking on pages with no sensitive actions
UI and UX bugs and spelling mistakes
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
Attacks requiring MITM or physical access to a user's device
Previously known vulnerable libraries without a working Proof of Concept
Comma Separated Values (CSV) injection without demonstrating a vulnerability
Missing best practices in SSL/TLS configuration
Any activity that could lead to the disruption of our service (DoS)
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
Rate limiting or bruteforce issues on non-authentication endpoints
Missing best practices in Content Security Policy
HttpOnly or Secure flags on cookies
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc)
Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors)
Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis
Tabnabbing
Open redirect - unless an additional security impact can be demonstrated
Issues that require unlikely user interaction
Vulnerabilities relying highly on social engineering aspect
Username enumeration
Vulnerabilities relying on the existence of plugins such as Flash
Security headers/attributes missing such as, but not limited to “content-type-options”, “X-XSS-Protection”
CAPTCHAs missing as a Security protection mechanism
Use of a known-vulnerable library without proof of exploitability;
Vulnerabilities in third-party software, libraries and code
Self-type Cross Site Scripting / Self-XSS
Cache Poisoning
Vulnerabilities on sites hosted by third parties unless they lead to a vulnerability on the main website
Vulnerabilities contingent on physical attack, social engineering, spamming, DDOS attacks, etc
Scope
*.
Other domains owned by Sprinklr, Inc
Safe Harbor
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
Thank you for helping keep Sprinklr safe!