CVE-2026-40230
Received Received - Intake
Stored XSS in Helpy Knowledge Base Doc

Publication date: 2026-04-29

Last updated on: 2026-05-01

Assigner: Fluid Attacks

Description
Helpy contains a stored cross-site scripting vulnerability in the knowledge base Doc rendering logic. An authenticated attacker with admin or agent editor privileges can persist arbitrary HTML or JavaScript in the body field of a knowledge base Doc.This issue affects helpy: 2.8.0.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-29
Last Modified
2026-05-01
Generated
2026-05-07
AI Q&A
2026-04-29
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
helpy.io helpy 2.8.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a stored cross-site scripting (XSS) issue found in Helpy version 2.8.0. It occurs in the knowledge base document rendering logic, where an authenticated attacker with admin or agent editor privileges can insert and persist arbitrary HTML or JavaScript code in the body field of a knowledge base document.


How can this vulnerability impact me? :

The vulnerability allows an attacker with certain privileges to execute arbitrary HTML or JavaScript code within the application. This can lead to unauthorized actions, data theft, session hijacking, or other malicious activities performed in the context of the affected application.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows an authenticated attacker with admin or agent editor privileges to inject malicious JavaScript or HTML into knowledge base documents, which is then executed in the browsers of users viewing those documents, including unauthenticated visitors.

This stored cross-site scripting (XSS) vulnerability could lead to unauthorized access to sensitive information or session hijacking, potentially compromising the confidentiality and integrity of user data.

Such security weaknesses may impact compliance with data protection regulations like GDPR and HIPAA, which require appropriate safeguards to protect personal and sensitive data from unauthorized access or disclosure.

However, the provided information does not explicitly discuss the direct impact of this vulnerability on compliance with these standards.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by inspecting knowledge base documents for the presence of malicious or unexpected HTML or JavaScript code in the body field, especially those created or edited by users with admin or agent editor privileges.

Since the vulnerability involves stored cross-site scripting in the Doc rendering logic, detection involves reviewing the database entries for knowledge base documents to identify any suspicious script tags or HTML content.

There are no specific commands provided in the resources to detect this vulnerability automatically.


What immediate steps should I take to mitigate this vulnerability?

As of the disclosure date, there is no available patch to address this vulnerability.

Immediate mitigation steps include restricting or reviewing admin and agent editor privileges to trusted users only, to reduce the risk of malicious document creation.

Additionally, manually auditing and sanitizing knowledge base documents to remove any malicious scripts or HTML can help mitigate exploitation.

Monitoring user activity and limiting access to the document creation or editing interfaces can also reduce risk.


Can you explain this vulnerability to me?

CVE-2026-40230 is a stored cross-site scripting (XSS) vulnerability in Helpy version 2.8.0. An authenticated attacker with admin or agent editor privileges can inject malicious JavaScript or HTML into the body field of a knowledge base document.

This malicious content is stored in the database without proper sanitization and later rendered in the browser of any user viewing the document, including unauthenticated visitors.

The vulnerability arises because the method responsible for sanitizing document content incorrectly marks it as safe for rendering without actual sanitization, and the Markdown-to-HTML conversion preserves raw HTML tags, allowing malicious scripts to pass through.

As a result, the stored malicious payload executes when the document is viewed, bypassing Rails' auto-escaping protections.


How can this vulnerability impact me? :

This vulnerability allows an attacker with certain privileges to inject malicious scripts that execute in the browsers of users viewing the affected knowledge base documents.

  • Execution of arbitrary JavaScript can lead to theft of user credentials or session tokens.
  • It can enable unauthorized actions on behalf of users, such as changing settings or accessing sensitive information.
  • The attack can affect both authenticated and unauthenticated users who view the compromised documents.

Overall, this can compromise the security and integrity of the application and its users.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by inspecting knowledge base documents in Helpy version 2.8.0 for the presence of malicious or unexpected HTML or JavaScript code in the body field. Since the vulnerability involves stored cross-site scripting, checking the database entries for the knowledge base documents for suspicious script tags or HTML content is a key detection method.

There are no specific commands provided to detect this vulnerability automatically. However, manual inspection or custom scripts to query the database for suspicious content in the Doc#body field can be used.

Additionally, monitoring HTTP traffic for unexpected script execution when viewing knowledge base documents could help identify exploitation attempts.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include restricting access to the admin or agent editor roles to trusted users only, as the vulnerability requires authenticated users with these privileges to inject malicious content.

Since there is no available patch as of the disclosure date, avoid creating or editing knowledge base documents until a fix is released.

Implement additional input sanitization or filtering on the body field of knowledge base documents to prevent the inclusion of arbitrary HTML or JavaScript.

Monitor and audit knowledge base documents for suspicious content and remove any potentially malicious entries.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart