CVE-2018-7274: Yab Quarx persistent cross-site scripting vulnerability
Summary
CVE-2018-7274: Yab Quarx persistent cross-site scripting vulnerability. Affects yab/quarx versions < 2.4.5. Fixed in 2.4.5. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Yab Quarx is a package available on Packagist that provides functionality for creating and managing blogs, FAQs, pages, widgets, and menus. It is prone to multiple persistent cross-site scripting vulnerabilities in various components such as the blog title, FAQ question, page title, widget name, and menu name.
Vulnerability Detail
The vulnerability allows an attacker to inject malicious scripts into the affected components, which can then be executed by unsuspecting users. This can lead to various security risks, including unauthorized access to sensitive information, session hijacking, and the potential for further exploitation of the affected system. The vulnerability has a CVSS score of 6.1, indicating a moderate severity level.
How To Fix
Minimum fixed version
2.4.5
This is the first release that contains the fix.
composer require yab/quarx:2.4.5
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Conclusion
Yab Quarx is prone to multiple persistent cross-site scripting vulnerabilities that can be mitigated by updating to version 2.4.5 or later. It is important for users of this package to promptly update their installations to ensure the security of their systems. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for yab/quarx →
FAQ
The vulnerability allows an attacker to execute arbitrary scripts on the affected system, potentially leading to unauthorized access, data theft, and further exploitation.
No, the recommended solution is to update to the latest version of Yab Quarx that includes the necessary patches.
No, versions prior to 2.4.5 are affected. It is recommended to update to version 2.4.5 or later.
There is no information available regarding active exploitation of this vulnerability at the moment.
For more information, you can refer to the GitHub Advisory Database entry for this vulnerability: [link].
References
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.