Vulnerabilities

The InWave Jobs plugin for WordPress is vulnerable to privilege escalation via password reset in all versions up to, and including, 3.5.1. This is due to the plugin not properly validating a user's identity prior to updating their password. This makes it possible for unauthenticated attackers to change arbitrary user's passwords, including administrators, and leverage that to gain access to their account.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> usb: gadget: core: flush gadget workqueue after device removal<br /> <br /> device_del() can lead to new work being scheduled in gadget-&gt;work<br /> workqueue. This is observed, for example, with the dwc3 driver with the<br /> following call stack:<br /> device_del()<br /> gadget_unbind_driver()<br /> usb_gadget_disconnect_locked()<br /> dwc3_gadget_pullup()<br /> dwc3_gadget_soft_disconnect()<br /> usb_gadget_set_state()<br /> schedule_work(&amp;gadget-&gt;work)<br /> <br /> Move flush_work() after device_del() to ensure the workqueue is cleaned<br /> up.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> io_uring/kbuf: reallocate buf lists on upgrade<br /> <br /> IORING_REGISTER_PBUF_RING can reuse an old struct io_buffer_list if it<br /> was created for legacy selected buffer and has been emptied. It violates<br /> the requirement that most of the field should stay stable after publish.<br /> Always reallocate it instead.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop<br /> <br /> Move the conditional loading of hardware DR6 with the guest&amp;#39;s DR6 value<br /> out of the core .vcpu_run() loop to fix a bug where KVM can load hardware<br /> with a stale vcpu-&gt;arch.dr6.<br /> <br /> When the guest accesses a DR and host userspace isn&amp;#39;t debugging the guest,<br /> KVM disables DR interception and loads the guest&amp;#39;s values into hardware on<br /> VM-Enter and saves them on VM-Exit. This allows the guest to access DRs<br /> at will, e.g. so that a sequence of DR accesses to configure a breakpoint<br /> only generates one VM-Exit.<br /> <br /> For DR0-DR3, the logic/behavior is identical between VMX and SVM, and also<br /> identical between KVM_DEBUGREG_BP_ENABLED (userspace debugging the guest)<br /> and KVM_DEBUGREG_WONT_EXIT (guest using DRs), and so KVM handles loading<br /> DR0-DR3 in common code, _outside_ of the core kvm_x86_ops.vcpu_run() loop.<br /> <br /> But for DR6, the guest&amp;#39;s value doesn&amp;#39;t need to be loaded into hardware for<br /> KVM_DEBUGREG_BP_ENABLED, and SVM provides a dedicated VMCB field whereas<br /> VMX requires software to manually load the guest value, and so loading the<br /> guest&amp;#39;s value into DR6 is handled by {svm,vmx}_vcpu_run(), i.e. is done<br /> _inside_ the core run loop.<br /> <br /> Unfortunately, saving the guest values on VM-Exit is initiated by common<br /> x86, again outside of the core run loop. If the guest modifies DR6 (in<br /> hardware, when DR interception is disabled), and then the next VM-Exit is<br /> a fastpath VM-Exit, KVM will reload hardware DR6 with vcpu-&gt;arch.dr6 and<br /> clobber the guest&amp;#39;s actual value.<br /> <br /> The bug shows up primarily with nested VMX because KVM handles the VMX<br /> preemption timer in the fastpath, and the window between hardware DR6<br /> being modified (in guest context) and DR6 being read by guest software is<br /> orders of magnitude larger in a nested setup. E.g. in non-nested, the<br /> VMX preemption timer would need to fire precisely between #DB injection<br /> and the #DB handler&amp;#39;s read of DR6, whereas with a KVM-on-KVM setup, the<br /> window where hardware DR6 is "dirty" extends all the way from L1 writing<br /> DR6 to VMRESUME (in L1).<br /> <br /> L1&amp;#39;s view:<br /> ==========<br /> <br /> CPU 0/KVM-7289 [023] d.... 2925.640961: kvm_entry: vcpu 0<br /> A: L1 Writes DR6<br /> CPU 0/KVM-7289 [023] d.... 2925.640963: : Set DRs, DR6 = 0xffff0ff1<br /> <br /> B: CPU 0/KVM-7289 [023] d.... 2925.640967: kvm_exit: vcpu 0 reason EXTERNAL_INTERRUPT intr_info 0x800000ec<br /> <br /> D: L1 reads DR6, arch.dr6 = 0<br /> CPU 0/KVM-7289 [023] d.... 2925.640969: : Sync DRs, DR6 = 0xffff0ff0<br /> <br /> CPU 0/KVM-7289 [023] d.... 2925.640976: kvm_entry: vcpu 0<br /> L2 reads DR6, L1 disables DR interception<br /> CPU 0/KVM-7289 [023] d.... 2925.640980: kvm_exit: vcpu 0 reason DR_ACCESS info1 0x0000000000000216<br /> CPU 0/KVM-7289 [023] d.... 2925.640983: kvm_entry: vcpu 0<br /> <br /> CPU 0/KVM-7289 [023] d.... 2925.640983: : Set DRs, DR6 = 0xffff0ff0<br /> <br /> L2 detects failure<br /> CPU 0/KVM-7289 [023] d.... 2925.640987: kvm_exit: vcpu 0 reason HLT<br /> L1 reads DR6 (confirms failure)<br /> CPU 0/KVM-7289 [023] d.... 2925.640990: : Sync DRs, DR6 = 0xffff0ff0<br /> <br /> L0&amp;#39;s view:<br /> ==========<br /> L2 reads DR6, arch.dr6 = 0<br /> CPU 23/KVM-5046 [001] d.... 3410.005610: kvm_exit: vcpu 23 reason DR_ACCESS info1 0x0000000000000216<br /> CPU 23/KVM-5046 [001] ..... 3410.005610: kvm_nested_vmexit: vcpu 23 reason DR_ACCESS info1 0x0000000000000216<br /> <br /> L2 =&gt; L1 nested VM-Exit<br /> CPU 23/KVM-5046 [001] ..... 3410.005610: kvm_nested_vmexit_inject: reason: DR_ACCESS ext_inf1: 0x0000000000000216<br /> <br /> CPU 23/KVM-5046 [001] d.... 3410.005610: kvm_entry: vcpu 23<br /> CPU 23/KVM-5046 [001] d.... 3410.005611: kvm_exit: vcpu 23 reason VMREAD<br /> CPU 23/KVM-5046 [001] d.... 3410.005611: kvm_entry: vcpu 23<br /> CPU 23/KVM-5046 [001] d.... 3410.<br /> ---truncated---

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

The Platform.ly for WooCommerce plugin for WordPress is vulnerable to Blind Server-Side Request Forgery in all versions up to, and including, 1.1.6 via the &amp;#39;hooks&amp;#39; function. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

The Hero Maps Premium plugin for WordPress is vulnerable to SQL Injection via several AJAX actions in all versions up to, and including, 2.3.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

The Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the accent_color and background parameter in all versions up to, and including, 1.6.8.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

The Golo - City Travel Guide WordPress Theme theme for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 1.6.10. This is due to the plugin not properly validating a user&amp;#39;s identity prior to updating their password. This makes it possible for unauthenticated attackers to change arbitrary user&amp;#39;s passwords, including administrators, and leverage that to gain access to their account.

The School Management System for Wordpress plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 93.0.0. This is due to the plugin not properly validating a user&amp;#39;s identity prior to updating their details like email and password through the mj_smgt_update_user() and mj_smgt_add_admission() functions, along with a local file inclusion vulnerability. This makes it possible for authenticated attackers, with student-level access and above, to change arbitrary user&amp;#39;s email addresses and passwords, including administrators, and leverage that to gain access to their account. This was escalated four months ago after no response to our initial outreach, yet it still vulnerable.

The School Management System for Wordpress plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the &amp;#39;mj_smgt_remove_feetype&amp;#39; and &amp;#39;mj_smgt_remove_category_new&amp;#39; AJAX actions in all versions up to, and including, 93.0.0. This makes it possible for unauthenticated attackers to delete arbitrary posts.

The School Management System for Wordpress plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the &amp;#39;title&amp;#39; parameter in all versions up to, and including, 93.0.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.