VulDB Recent Entries

A vulnerability categorized as problematic has been discovered in gVectors wpForo Forum up to 2.4.15. This issue affects some unknown processing of the component SVG File Parser. Executing a manipulation can lead to cross site scripting. This vulnerability is handled as CVE-2026-28558. The attack can be executed remotely. There is not any exploit available. It is advisable to upgrade the affected component.

A vulnerability was found in gVectors wpForo Forum up to 2.4.15. It has been rated as critical. This vulnerability affects the function topic_move/topic_merge/topic_split. Performing a manipulation results in missing authorization. This vulnerability is known as CVE-2026-28556. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is advised.

A vulnerability was found in gVectors wpForo Forum up to 2.4.15. It has been declared as critical. This affects the function wpforo_close_ajax. Such manipulation leads to missing authorization. This vulnerability is traded as CVE-2026-28555. The attack may be launched remotely. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability was found in gVectors wpForo Forum up to 2.4.15. It has been classified as critical. Affected by this issue is the function wpforo_approve_ajax of the component AJAX Handler. This manipulation causes missing authorization. This vulnerability appears as CVE-2026-28554. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended.

A vulnerability was found in gVectors wpForo Forum up to 2.4.14 and classified as critical. Affected by this vulnerability is the function Topics::get_topics. The manipulation of the argument wpfob results in sql injection. This vulnerability is reported as CVE-2026-28562. The attack can be launched remotely. No exploit exists. It is suggested to upgrade the affected component.

A vulnerability has been found in gVectors wpForo Forum up to 2.4.15 and classified as critical. Affected is the function wpforo_synch_roles of the component AJAX Handler. The manipulation leads to missing authorization. This vulnerability is documented as CVE-2026-28557. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.

A vulnerability, which was classified as critical, was found in MaxSite CMS up to 109.1. This impacts the function eval of the file application/maxsite/admin/plugins/editor_markitup/preview-ajax.php of the component MarkItUp Preview AJAX Endpoint. Executing a manipulation can lead to code injection. This vulnerability is registered as CVE-2026-3395. It is possible to launch the attack remotely. Furthermore, an exploit is available. You should upgrade the affected component. The code maintainer was informed beforehand about the issues. He reacted very fast and highly professional.

A vulnerability, which was classified as problematic, has been found in jarikomppa soloud up to 20200207. This affects the function SoLoud::Wav::loadwav of the file src/audiosource/wav/soloud_wav.cpp of the component WAV File Parser. Performing a manipulation results in memory corruption. This vulnerability is cataloged as CVE-2026-3394. The attack must be initiated from a local position. Furthermore, there is an exploit available. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability classified as problematic was found in jarikomppa soloud up to 20200207. The impacted element is the function SoLoud::Wav::loadflac of the file src/audiosource/wav/soloud_wav.cpp of the component Audio File Handler. Such manipulation leads to heap-based buffer overflow. This vulnerability is listed as CVE-2026-3393. The attack must be carried out locally. In addition, an exploit is available. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability classified as problematic has been found in FascinatedBox lily up to 2.3. The affected element is the function eval_tree of the file src/lily_emitter.c. This manipulation causes null pointer dereference. This vulnerability is tracked as CVE-2026-3392. The attack is restricted to local execution. Moreover, an exploit is present. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability described as problematic has been identified in FascinatedBox lily up to 2.3. Impacted is the function clear_storages of the file src/lily_emitter.c. The manipulation results in out-of-bounds read. This vulnerability is identified as CVE-2026-3391. The attack is only possible with local access. Additionally, an exploit exists. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability marked as problematic has been reported in FascinatedBox lily up to 2.3. This issue affects the function patch_line_end of the file src/lily_build_error.c of the component Error Reporting. The manipulation leads to out-of-bounds read. This vulnerability is referenced as CVE-2026-3390. The attack can only be performed from a local environment. Furthermore, an exploit is available. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability labeled as problematic has been found in Squirrel up to 3.2. This vulnerability affects the function sqstd_rex_newnode in the library sqstdlib/sqstdrex.cpp. Executing a manipulation can lead to null pointer dereference. The identification of this vulnerability is CVE-2026-3389. The attack can only be executed locally. Furthermore, there is an exploit available. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability identified as problematic has been detected in Squirrel up to 3.2. This affects the function SQCompiler::Factor/SQCompiler::UnaryOP of the file squirrel/sqcompiler.cpp. Performing a manipulation results in uncontrolled recursion. This vulnerability was named CVE-2026-3388. The attack needs to be approached locally. In addition, an exploit is available. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability categorized as problematic has been discovered in wren-lang wren up to 0.4.0. Affected by this issue is the function getByteCountForArguments of the file src/vm/wren_compiler.c. Such manipulation leads to null pointer dereference. This vulnerability is uniquely identified as CVE-2026-3387. Local access is required to approach this attack. Moreover, an exploit is present. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability was found in wren-lang wren up to 0.4.0. It has been rated as problematic. Affected by this vulnerability is the function emitOp of the file src/vm/wren_compiler.c. This manipulation causes out-of-bounds read. This vulnerability is handled as CVE-2026-3386. It is possible to launch the attack on the local host. Additionally, an exploit exists. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability was found in wren-lang wren up to 0.4.0. It has been declared as problematic. Affected is the function resolveLocal of the file src/vm/wren_compiler.c. The manipulation results in uncontrolled recursion. This vulnerability is known as CVE-2026-3385. Attacking locally is a requirement. Furthermore, an exploit is available. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability was found in ChaiScript up to 6.1.0. It has been classified as problematic. This impacts the function chaiscript::eval::AST_Node_Impl::eval/chaiscript::eval::Function_Push_Pop of the file include/chaiscript/language/chaiscript_eval.hpp. The manipulation leads to uncontrolled recursion. This vulnerability is traded as CVE-2026-3384. An attack has to be approached locally. Furthermore, there is an exploit available. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability was found in ChaiScript up to 6.1.0 and classified as problematic. This affects the function chaiscript::Boxed_Number::go of the file include/chaiscript/dispatchkit/boxed_number.hpp. Executing a manipulation can lead to divide by zero. This vulnerability appears as CVE-2026-3383. The attack requires local access. In addition, an exploit is available. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability has been found in ChaiScript up to 6.1.0 and classified as problematic. The impacted element is the function chaiscript::Boxed_Number::get_as of the file include/chaiscript/dispatchkit/boxed_number.hpp. Performing a manipulation results in memory corruption. This vulnerability is reported as CVE-2026-3382. The attack requires a local approach. Moreover, an exploit is present. The project was informed of the problem early through an issue report but has not responded yet.