CVE-2017-16636 Cross-site scripting in n/a
Attackers can inject persistent XSS via unrecognized editor tags to compromise higher-privilege user accounts in Bludit CMS.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2017-16636?
CVE-2017-16636 is a medium-severity cross-site scripting vulnerability in n/a, published on 6 Nov 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
In Bludit v1.5.2 and v2.0.1, an XSS vulnerability is located in the new page, new category, and edit post function body message context. Remote attackers are able to bypass the basic editor validation to trigger cross site scripting. The XSS is persistent and the request method to inject via editor is GET. To save the editor context, the followup POST method request must be processed to perform the attack via the application side. The basic validation of the editor does not allow injecting script codes and blocks the context. Attackers can inject the code by using an editor tag that is not recognized by the basic validation. Thus allows a restricted user account to inject malicious script code to perform a persistent attack against higher privilege web-application user accounts.
Weakness: CWE-79
Which versions are affected by CVE-2017-16636?
It affects 1 product.
Products include Bludit Bludit.
How do I fix CVE-2017-16636?
No fix has been published for CVE-2017-16636 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2017-16636 being exploited?
There is no known exploitation of CVE-2017-16636 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-w3pq-253h-3gfp.