Bludit Bludit 1.5.2
Approved changes feed: RSS · Atom
cpe:2.3:a:bludit:bludit:1.5.2:*:*:*:*:*:*:*
part: a version: 1.5.2 update: *
| Vendor | Bludit (67bdaa9c-b7c5-5830-82a9-c3e7bf8573ca) |
|---|---|
| Product | Bludit (4c1d3b44-ab61-5860-bb04-857b81b46310) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/bludit/bludit |
purl2cpe | 2026-06-01 10:17:12.034841 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2017-16636 |
vulnerable | 2026-06-08 05:09:00.673051 |
Details available
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.
Published: 2017-11-06T22:00:00.000Z
Updated: 2024-08-05T20:27:04.305Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.