CVE-2026-4175: Aureus ERP Chatter Message content-text-entry.blade.php cross site scripting
A vulnerability was determined in Aureus ERP up to 1.3.0-BETA1. The affected element is an unknown function of the file plugins/webkul/chatter/resources/views/filament/infolists/components/messages/content-text-entry.blade.php of the component Chatter Message Handler. Executing a manipulation of the argument subject/body can lead to cross site scripting. The attack can be launched remotely. Upgrading to version 1.3.0-BETA1 is sufficient to fix this issue. This patch is called 2135ee7efff4090e70050b63015ab5e268760ec8. It is suggested to upgrade the affected component.
Other sources
A vulnerability was determined in Aureus ERP up to 1.3.0-BETA2. The affected element is an unknown function of the file plugins/webkul/chatter/resources/views/filament/infolists/components/messages/content-text-entry.blade.php of the component Chatter Message Handler. Executing a manipulation of the argument subject/body can lead to cross site scripting. The attack can be launched remotely. Upgrading to version 1.3.0-BETA1 is sufficient to fix this issue. This patch is called 2135ee7efff4090e70050b63015ab5e268760ec8. It is suggested to upgrade the affected component.
— NVD
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-4175?
CVE-2026-4175 is classified as a cross-site scripting vulnerability that poses a high risk to users of Aureus ERP up to version 1.3.0-BETA2.
How do I fix CVE-2026-4175?
To mitigate CVE-2026-4175, upgrade Aureus ERP to the latest version that addresses this security flaw.
What are the potential impacts of CVE-2026-4175?
If exploited, CVE-2026-4175 may allow attackers to inject malicious scripts leading to unauthorized actions or data theft.
Which versions of Aureus ERP are affected by CVE-2026-4175?
CVE-2026-4175 affects Aureus ERP versions up to and including 1.3.0-BETA2.
Is there a workaround for CVE-2026-4175 until I can update?
Currently, the recommended action is to update to a patched version, as no known effective workaround exists for CVE-2026-4175.