Man-in-the-middle tampering with the Automatic Update channel in Zhonglun CloudPOS 3.0 lets an unauthenticated attacker who holds a non-endpoint position on the network path manipulate the version, url, packagekey and package-name arguments processed in Program.cs, potentially steering or altering the update flow. Exploitation requires no authentication and no user interaction, but VulDB rates the attack as highly complex and the practical difficulty of occupying the required interception position keeps the overall priority low, with only low confidentiality, integrity and availability impact. Publicly available exploit code exists (a proof-of-concept document is linked from the VulDB record), the issue is not listed in CISA KEV so there is no confirmation of active exploitation, and the vendor was contacted early but did not respond.
SQL injection in the editassid parameter of managevideos2.php in mathurvishal's CloudClassroom-PHP-Project lets an authenticated low-privilege user supply crafted input that is concatenated into a backend SQL query, allowing them to read from or modify the application's database. Publicly available exploit code exists (a proof-of-concept write-up is linked from the references), but there is no confirmed active exploitation in the wild and no CISA KEV listing; the provided CVSS 4.0 score is 2.1 and the independent re-assessment scores it as CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L, treating it as a low real-world priority because valid credentials and a deployed instance of this niche, rolling-release PHP application are both required. The maintainer was contacted about the flaw and did not respond, and because the project ships as a rolling release there is no versioned affected or fixed release to point to.
Improper privilege management in Krayin laravel-crm up to and including 2.2.5 lets an authenticated back-office user who can reach the Settings > Users/Roles area escalate their own privileges by manipulating the role_id argument handled in packages/Webkul/Admin/src/Http/Controllers/Settings/UserController.php. The pre-patch code applies no canManageRole() authorization check and does not block a user from editing the role assigned to their own account or from creating/updating a role carrying permissions broader than their own, so a low-privileged account can grant itself full administrative rights. Publicly available exploit code exists (a proof-of-concept advisory has been published and the issue is tracked on GitHub), while the vendor assigns a modest CVSS 4.0 score of 2.1; exploitation still requires valid credentials for a settings-capable account, so this is a targeted, post-authentication privilege-escalation risk rather than an unauthenticated compromise.
SQL injection in the updatestudent.php script of mathurvishal's CloudClassroom-PHP-Project lets an authenticated attacker inject arbitrary SQL through the unsanitized 'eno' parameter, allowing them to read or manipulate student records in the underlying database. The product is an unversioned educational PHP project hosted on GitHub, so all commits up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be are presumed affected and no fixed release exists. Publicly available exploit code exists (referenced from a GitHub repository alongside the VulDB entry), the vendor was contacted but never responded, and no CISA KEV entry indicates confirmed active exploitation.
Cross-site request forgery in ningzichun's student-management-system (up to commit 98760f5711cf6dc8b4adca53a9e207ca49b02ebf) lets an unauthenticated attacker forge state-changing requests that execute in the browser of a logged-in administrator or user, producing a limited integrity-only modification. Exploitation requires the victim to hold an active session and be socially engineered into visiting an attacker-controlled page or clicking a crafted link (UI:P/UI:R); confidentiality and availability are unaffected. Publicly available exploit code exists and the CVE carries an EPSS-relevant proof-of-concept flag, though there is no confirmed active exploitation (CISA KEV), and the upstream project was notified via an issue report but has not responded and has released no fix.
Reflected cross-site scripting in ningzichun student-management-system allows unauthenticated remote attackers to inject arbitrary script into the admin/fun/addLog.php log entry function via the reason or detail parameters; exploitation requires a victim to interact with a crafted link, and publicly available exploit code exists. The flaw is rated CVSS 4.0 5.3 (Medium) with no privileges required but user interaction, and independent assessment confirms it is limited to integrity impact with no direct confidentiality or availability loss. The project maintainer has not responded to the reported issue, and no vendor patch is identified at time of analysis.
Cross-site scripting in Krayin Laravel CRM through 2.2.5 lets an authenticated user with access to the admin configuration/settings panel upload a crafted SVG image containing embedded script that executes when a victim later views the rendered file. Exploitation requires a valid account with configuration access plus victim interaction (the victim must view a page that renders the uploaded SVG inline), which keeps this a low-severity, low-priority issue even though it is remotely reachable; publicly available exploit code exists, and there is no confirmation of active exploitation. The vendor resolved the flaw in 2.2.6 by removing SVG from the upload mime allowlist and resolving validation rules only from trusted server-side configuration.
Authorization bypass in Sanluan PublicCMS up to and including 6.202506.e lets an authenticated administrative user read user and department records outside their authorized scope by tampering with the userId or deptId parameter handled by the exportExcel/exportData functions. Because the server never verifies that the requested identifier falls within the caller's own department or permission scope (CWE-639), a low-privileged backend account can pull exports it should not see; the impact is confidentiality-only with no modification or denial-of-service component. Publicly available exploit code exists (a PoC published in the GitHub CVERequest repository), but the flaw is not confirmed actively exploited (CISA KEV), the vendor did not respond to the disclosure, and no vendor patch is available - making this a low-priority issue despite being remotely reachable.
Default-credential exposure in ningzichun's student-management-system allows remote attackers to authenticate with the administrator password shipped in the example_lite.sql seed file, obtaining full access to the application's administrative functionality and stored data. The flaw affects all versions up to commit 98760f5711cf6dc8b4adca53a9e207ca49b02ebf, and publicly available exploit code exists, though no CISA KEV listing or other confirmation of active exploitation is present. Exploitation is entirely gated on the operator having initialized the database from example_lite.sql and never rotated the seeded account password; given that this is an obscure, rarely deployed hobby project, overall real-world risk is low despite the moderate 5.1 CVSS 4.0 score.
Stored cross-site scripting in sheshbabu zen (versions 1.0 through 1.5.0) allows an authenticated low-privilege user to store crafted content that is later rendered by features/notes/NotesEditor.jsx through React's dangerouslySetInnerHTML without sanitization, executing script in the browser of anyone who opens the affected note. Publicly available exploit code exists, and the vendor was contacted about the disclosure but did not respond, so no vendor-released patch has been identified. Impact is limited to integrity in the affected web origin (scope change, low confidentiality/integrity, no availability impact), which keeps this a low-to-moderate priority issue for self-hosted instances.
Deserialization of untrusted data in the LangChain4j-agentic module's AgenticScopeSerializer.fromJson path allows an attacker who can already write to an AgenticScope persistence store to trigger arbitrary class instantiation through Jackson's insecure default typing. Affected versions are the 1.5.3, 1.11.10 and 1.18.1 beta lines up to and including 1.5.3-beta10, 1.11.10-beta18 and 1.18.1-beta27, with fixes released in 1.5.3-beta11, 1.11.10-beta19 and 1.18.1-beta28 under advisory GHSA-gmwr-7wmf-mrjm. Publicly available exploit code exists, but effective risk is low: exploitation requires that the application have explicitly enabled AgenticScope persistence (opt-in and off by default) and that the attacker already control the writable backing store, with attack complexity rated high; this issue is not confirmed actively exploited (not in CISA KEV), and EPSS-style scoring is negligible given the reported CVSS base of 2.1.
Bypass of failed-login rate limiting in django-allauth before 65.19.4 allows unauthenticated remote attackers to obtain a higher effective number of login attempts in certain common configurations by submitting diacritic variants of the same username or email. The flaw is a low-severity defense-in-depth weakness, not a directly exploitable breach: CVSS 3.1 score 3.7 with AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N, requiring specific normalization and rate-limit configuration behavior; it does not grant access without an underlying weak or guessable credential. Vendor-released patch: 65.19.4. No public exploit identified at time of analysis, and no CISA KEV active-exploitation confirmation was provided.
GraphQL query injection in Rapid7 Bulk Export MCP 0.2.5 through 0.6.1 allows an authenticated high-privileged actor who can influence the export_id argument used by the check_rapid7_export_status and download_rapid7_export tools to terminate the intended export(id: "...") selection and append attacker-controlled root-level selections such as schema introspection. The impact is confined to confidentiality (CVSS 2.7, CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N), because every injected query executes inside the operator's own already-authenticated Rapid7 API key scope and cannot cross a tenant or account boundary - a directly-malicious operator gains nothing beyond what direct API access already provides, so realistic exposure requires a compromised or careless upstream MCP client or indirect prompt injection forwarding an unvalidated identifier. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; the vendor-released fix is version 0.6.2, which parameterizes export_id as a GraphQL variable.
Hard-coded cryptographic key material embedded in the Tohoku Electric Power 'Yorisou e Net' Android and iOS apps can be recovered by inspecting or reverse-engineering the installed application package, potentially exposing whatever data or service that key protects. Both mobile builds are affected (per the vendor CPE entries), and the CVSS vector indicates physical access to the device (AV:P) with no authentication (PR:N) and no user interaction (UI:N) required, so the practical gate is simply obtaining and analyzing the app rather than any remote precondition. Impact is confined to a low-confidence confidentiality loss (C:L, no integrity or availability effect) and the advisory does not specify what the recovered key protects downstream; all signals point to a low-priority issue, with no public exploit code identified at time of analysis and no EPSS or KEV data provided. The JVN advisory JVN93985674 is the primary coordinated-disclosure reference.
Stale OAuth authentication-mechanism preferences can survive a logout in the RabbitMQ management UI on versions 4.2.0 through 4.2.7 and 4.3.0/4.3.1, because the plugin emits a non-ASCII cookie name when it tries to clear the strict_auth_mechanism or preferred_auth_mechanism cookie, and RFC 6265-compliant browsers refuse to delete a cookie whose name is not a valid token. The practical effect is limited to a persisted UI preference carrying across logout/login cycles; there is no code execution, data exfiltration, or confidentiality or availability impact, which is consistent with the NVD CVSS 4.0 base score of 2.3 and with the independent CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N assessment. Exploitation requires the management UI to be in active use and a logout/login cycle to occur, and no public exploit code or evidence of active exploitation was identified at time of analysis.
Authenticated agents on Zammad helpdesk instances can retrieve the AI provider error strings recorded for AI analytics runs belonging to tickets they are not authorized to view, simply by passing an arbitrary ai_analytics_run_error_id to the ticket summarize endpoint. The exposure is confined to the stored provider error message - no ticket content, customer data, or conversation text is disclosed - and the AI summarize/analytics feature must be in use with at least one errored run present for the attack to succeed. The vendor-published CVSS 4.0 score is 2.3 and our independent assessment rates it low severity, with only a limited confidentiality impact; no public exploit code or active exploitation has been identified at time of analysis, and the flaw is fixed in Zammad 7.1.2.
RabbitMQ OAuth credential refresh keeps revoked runtime tags on live AMQP connections in versions 3.13.0 up to the fixed 3.13.19, 4.0.24, 4.1.15, 4.2.10 and 4.3.5 releases, so an authenticated client (CVSS PR:L) that already held the privileged `impersonator` tag can keep publishing messages with a foreign AMQP userid after that privilege is withdrawn. The defect only affects connections that once held `impersonator` and then refresh in place to a same-username OAuth token that no longer grants it, with `rabbit_auth_backend_oauth2` (or an equivalent refresh-capable backend) enabled; a freshly opened connection using the downgraded token correctly refuses the same publish. No public exploit code has been identified at time of analysis, and the practical impact is a stale privilege-revocation gap for an already-privileged session rather than a route for an ordinary user to gain new privileges.
Authenticated peers connected to a Windows RustDesk host running a version before 1.5.0 can bypass the one-way file transfer setting and pull files straight out of the victim's clipboard. Because the same option that is meant to prevent the local machine from serving clipboard files is the one being ignored, an attacker who already holds a valid remote session can send crafted clipboard-redirection messages (FormatDataRequest / FileContentsRequest) and, by supplying the known FileGroupDescriptorW format identifier, receive the contents of any file the user has copied. Rated only 2.3 under CVSS v4.0 (assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), the issue yields confidentiality impact only, requires an authenticated peer relationship plus a clipboard that already holds files, and no public exploit has been identified at time of analysis.
Zammad helpdesk instances prior to 7.1.2 expose a legacy destroy_form action on AttachmentsController that deletes temporary UploadCache store records using only a caller-supplied form_id and performs no ownership verification (CWE-862), so an authenticated user who knows another user's pending-upload UUID can silently wipe that user's in-progress attachments before the ticket or article is submitted. Exploitation requires a valid account on the instance plus knowledge of the victim's non-enumerable form_id UUID and only affects files still in the transient pre-submission cache, which is why the base score is a low 2.3 under CVSS 4.0 (equivalently AV:N/AC:H/PR:L/UI:N/C:N/I:L/A:L on CVSS 3.1). No public exploit code or confirmed active exploitation was identified at time of analysis, and the flaw is fixed in Zammad 7.1.2.
Stored cross-site scripting in the MediaWiki Cargo extension through version 3.9.4 lets an authenticated user with content-editing privileges embed script payloads in Cargo-managed data that execute in the browser of any other user who later views the rendered Cargo output. The assessed severity is low, with a CVSS 4.0 base score of 2.3 and a 3.1 vector of AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N, so impact is confined to the victim's browser session (low confidentiality and integrity, no availability effect) and no public exploit identified at time of analysis. Because Cargo is an optional extension, only wikis that have it installed at 3.9.4 or earlier are affected, and each successful attack also requires a second user to view the poisoned page, which keeps attack complexity high.
Mutation XSS in the Elixir library LazyHTML 0.1.0 through 0.1.12 lets attacker-supplied markup slip past element and attribute allowlist filters and turn into live HTML when the filtered document is serialized for display. The defect is in LazyHTML.to_html/2 and LazyHTML.Tree.to_html/2, which decide whether to escape an element's text from the tag name alone, so a style or script element inside SVG or MathML foreign content is parsed with character references decoded yet serialized as an unescaped HTML raw-text element; encoded markup such as </style><img src=x onerror=...> inside <svg><style> therefore closes the element on re-parse and executes. Exploitation is unauthenticated and remote but conditional: the consumer application must parse untrusted HTML with lazy_html, filter the document or tree, and serialize the result to a victim who views it (user interaction required), which keeps real-world impact low (scope change, low confidentiality and integrity, no availability impact); no public exploit identified at time of analysis, and the vendor has shipped a fix in 0.1.13.
Information disclosure in the Zammad helpdesk knowledge base lets an authenticated user who holds the knowledge_base.editor permission in at least one category see answer titles and updated_at timestamps belonging to categories where they have no editor rights, exposed through the global quick search. The leak only occurs in deployments that use granular, per-category permission assignments with differing editor roles; category names are not exposed and opening a leaked answer returns 'Page not found,' so no answer body content is accessible. Exploitation requires a valid authenticated account with the editor permission (PR:L/H depending on the scoring system) and is rated low severity (CVSS 4.0 base 2.1), with no public exploit identified at time of analysis.
Administrator-tagged accounts on RabbitMQ can silently delete users that carry the 'protected' tag by calling the management plugin's POST /api/users/bulk-delete endpoint, which skips the protected-user guard that the single-user DELETE /api/users/:name path enforces. The flaw affects RabbitMQ 3.13.0 up to 3.13.14 and 4.0.x, 4.1.x, and 4.2.x releases before 4.0.20, 4.1.11, and 4.2.6, but only when the rabbitmq_management plugin is enabled and only for an attacker who already holds the highest management privilege ('administrator' tag), so the outcome is integrity loss (destruction of hardened service accounts) rather than any escalation of access. No public exploit identified at time of analysis, no confirmed active exploitation (CISA KEV), and no EPSS score was provided; the assessed CVSS:3.1 vector is AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N (CVSS 4.0 base 2.1), and realistic risk is confined to insider misuse, a compromised admin credential, or accidental bulk deletion.
Authenticated Zammad agents holding the ticket.agent permission can read knowledge base answer content they are not authorized to access by invoking the KnowledgeBase::Answer::Suggestion::Content::Transform GraphQL mutation with a translation ID outside their KB category permissions. This low-severity authorization bypass affects Zammad versions prior to 7.0.2 and requires the attacker to know a valid translation ID; it is fixed in 7.0.2 and no public exploit code or active exploitation has been identified at time of analysis.