CVE-2022-33009

MediumCVSS 4.8/10Last modified Jul 9, 2026

Description

A stored cross-site scripting (XSS) vulnerability in LightCMS v1.3.11 allows attackers to execute arbitrary web scripts or HTML via uploading a crafted PDF file.

Metrics

CVSS 3.1 4.8/10CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

Weakness enumeration

Affected software

No affected versions have been published.

Timeline

Published
Jun 27, 2022
Last modified
Jul 9, 2026
NVD status
Modified

Related CVEs from 2022

CVE-2022-33012.4Improper Cleanup on Thrown Exception in GitHub repository ikus060/rdiffweb prior to 2.4.8.CVE-2022-330118.8Known v1.3.1+2020120201 was discovered to allow attackers to perform an account takeover via a host header injection attack.CVE-2022-330128.8Microweber v1.2.15 was discovered to allow attackers to perform an account takeover via a host header injection attack.CVE-2022-33027.2The Spam protection, AntiSpam, FireWall by CleanTalk WordPress plugin before 5.185.1 does not validate ids before using them in a SQL statemCVE-2022-330217.5CVA6 commit 909d85a accesses invalid memory when reading the value of MHPMCOUNTER30.CVE-2022-330237.5CVA6 commit 909d85a gives incorrect permission to use special multiplication units when the format of instructions is wrong.CVE-2022-330247.5There is an Assertion `int decode_preR13_entities(BITCODE_RL, BITCODE_RL, unsigned int, BITCODE_RL, BITCODE_RL, Bit_Chain *, Dwg_Data *' faiCVE-2022-330257.8LibreDWG v0.12.4.4608 was discovered to contain a heap-use-after-free via the function decode_preR13_section at decode_r11.c.CVE-2022-330267.8LibreDWG v0.12.4.4608 was discovered to contain a heap buffer overflow via the function bit_calc_CRC at bits.c.CVE-2022-330277.8LibreDWG v0.12.4.4608 was discovered to contain a heap-use-after-free via the function dwg_add_handleref at dwg.c.CVE-2022-330287.8LibreDWG v0.12.4.4608 was discovered to contain a heap buffer overflow via the function dwg_add_object at decode.c.CVE-2022-33034.7A race condition flaw was found in the Linux kernel sound subsystem due to improper locking. It could lead to a NULL pointer dereference whi