Server-side request forgery in SparkyFitness (self-hosted AI health and fitness tracker) before version 1.6.0 lets an authenticated user point the built-in custom AI service configuration at arbitrary internal or private network addresses, causing the server to issue outbound POST requests carrying an attacker-controlled bearer token and to leak the AI system prompt. Exploitation requires a valid account and the ability to save a custom AI provider URL (custom, ollama, or openai_compatible) and then trigger an AI flow such as chat or the label/food-photo scan, matching the assessed vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N (5.4). No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis; impact is bounded to internal-service probing, forged outbound POSTs, and prompt disclosure rather than code execution. The issue is fixed in 1.6.0, which enforces an outbound URL policy that rejects private-network AI destinations with HTTP 403 by default.
Authenticated attackers holding only subscriber-level access can execute arbitrary WordPress shortcodes on sites running the WPEverest User Registration & Membership plugin in all versions up to and including 5.2.8, because an action passes an unvalidated value straight into do_shortcode without checking it first. The flaw is rated CVSS 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) and there is no public exploit identified at time of analysis - it is not confirmed actively exploited (CISA KEV). Impact is bounded, but the practical risk is elevated on the many sites that leave open user registration enabled, since an attacker can simply self-provision the required subscriber account and then trigger the vulnerable shortcode path; sites that disable open registration meaningfully reduce exposure.
IBM i releases 7.3, 7.4, 7.5 and 7.6 can allow a remote authenticated attacker to slip past the ChrootDirectory confinement that is supposed to isolate SSH/SFTP users, exposing files and data outside the directory they were meant to be restricted to. The weakness is entirely dependent on configuration: it only affects systems that explicitly set ChrootDirectory in sshd_config and rely on it as an isolation boundary, while default deployments without chroot confinement are not impacted. No public exploit code has been identified at time of analysis, and because a valid restricted-account credential is mandatory and the assessed impact is bounded to low confidentiality and integrity loss with no availability effect, this rates as a moderate, operator-dependent issue rather than an emergency.
Account takeover in Apache Answer through 2.0.2 is possible because email verification codes issued for one workflow are accepted by other, more sensitive workflows - the code's original purpose is not enforced at redemption time. An attacker who obtains or replays a currently valid code from a lower-sensitivity email flow can present it to a sensitive flow tied to a target account, yielding high confidentiality and integrity impact (assessed CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N, rated moderate by the project). Exploitation is constrained rather than trivial: the deployment must be using Apache Answer's email-code-based workflows and the attacker must hold a valid, unexpired code targeting a specific account workflow; no public exploit code or confirmed active exploitation was identified at time of analysis.
In applications that use the Microsoft Identity Web library for authentication and authorization, an attacker who already holds valid low-privilege credentials can tamper with authentication data the library incorrectly assumes is immutable, bypassing authorization checks to read data beyond their granted permissions (CVSS 5.3, C:H/I:N/A:N). Exploitation is not unauthenticated and is constrained by high attack complexity (AC:H), meaning specific conditions, state, or timing must be satisfied rather than a simple repeatable request. At the time of analysis there is no public exploit identified and no confirmed active exploitation, but a vendor patch is available (RL:O), so patched deployments are not affected.
Stored cross-site scripting in the Webhook URL form field of Crafty Controller allows an authenticated user with access to that configuration field to persist malicious input that executes in the browser of any other user who later views the affected page. The vulnerability is assessed at CVSS 5.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N), meaning a valid low-privileged account is required (PR:L) and a separate victim must load the rendering view (UI:R); the attacker cannot trigger impact on their own session, and no public exploit code was identified at time of analysis. Exploitation is most damaging when a higher-privileged operator such as an administrator views the poisoned webhook view, but this is a genuinely moderate, not high-priority, issue and no anonymous or pre-authentication path exists.
Authorization bypass in SmartCrawl (smartcrawl-seo) through version 3.16.4 allows an authenticated low-privilege user to manipulate a user-controlled key and access or modify data they should not be able to access, due to CWE-639 insecure direct object reference and incorrect access control configuration. This is a moderate-severity issue (CVSS 5.4, AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) whose real-world risk is constrained by the requirement for a valid low-privilege account; no public exploit identified at time of analysis, and no KEV or EPSS signal was provided. Sites running affected SmartCrawl versions should monitor the Patchstack advisory and update beyond 3.16.4 once a fixed release is confirmed.
Remote denial of service in libIEC61850 1.6.1 allows an unauthenticated network attacker to crash an MMS server that has the file service and ObtainFile operation enabled. A successful ObtainFile frees the task's file handle but leaves the stale non-NULL pointer in a task reset to the NOT_USED state; a subsequent ObtainFile that reuses that task and fails destination-file creation then closes the already-freed handle a second time (CWE-415 double free), aborting the server process. Exploitation requires a specific success-then-failure request sequence and reachability to the exposed MMS endpoint; no public exploit code has been identified at time of analysis, and impact is limited to availability (CVSS 5.3, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) with no data exposure. The flaw is confirmed fixed in version 1.6.2.
Sensitive information exposure in HUSKY - Products Filter for WooCommerce Professional through 1.4.5 allows unauthenticated attackers to extract the external MySQL host, database name, username, and plaintext password from the inline woof_tm_data script object on public frontend filter pages when the Statistics extension, saved external MySQL credentials, and Turbo Mode are all enabled. This is a moderate, conditional risk: default or internal-database configurations are not affected, and no public exploit was identified at time of analysis, but any site that has adopted those documented settings should treat the credentials as potentially exposed.
Authenticated file disclosure in Helical Insight through 7.0.0 lets a user with viewer-level privileges read files outside the solution directory through the path parameter of /getExternalResource, bypassing per-resource access control by supplying parent-directory segments. Exploitation requires a valid low-privilege session and is constrained to files carrying an allowed extension (js, json, html), so confidentiality impact is limited and there is no integrity or availability effect - matching the assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N and the assigned score of 5.3. No public exploit code was identified at time of analysis, the CVE is not listed in CISA KEV, and no EPSS probability was supplied; this is a medium-severity information-disclosure issue rather than an urgent priority.
Unbounded decoding of PMAPPROC_DUMP replies in libtirpc lets a malicious or already-compromised RPC portmapper exhaust the memory and CPU of a client application that calls pmap_getmaps(), crashing or stalling the client process and causing a denial of service. The exposure is conditional and client-side: a remote attacker cannot initiate the exchange, so the victim must direct libtirpc-based tooling (NFS/RPC mount helpers, discovery or inventory scanners) at the attacker-controlled rpcbind, which is why the assessed vector is AV:N/AC:H/PR:N/UI:R with availability-only impact and no confidentiality, integrity, or code-execution consequences. Affected packages are those shipped in Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4. At CVSS 5.3 this is a moderate-severity, low-priority issue in practice, and no public exploit code and no confirmed active exploitation (no CISA KEV listing) were identified at time of analysis.
Missing authorization in the Piranha CMS manager API (Piranha.Manager LanguageApiController) lets any authenticated manager user list, create, edit, and delete site languages even when their account lacks the granular Language, LanguageAdd, LanguageEdit, and LanguageDelete permissions. Affected deployments are Piranha CMS through version 12.2; the attacker must already hold a valid manager account and simply call the manager/api/language Get, Save, and Delete actions directly. Impact is confined to language configuration and the localized content that depends on it - deleted languages cause affected sites to fall back to the default language instance-wide, with no confidentiality exposure; no CVE is confirmed as actively exploited (CISA KEV) and no public exploit identified at time of analysis, though a public technical writeup and vendor advisory are available.
Authenticated low-privileged users in Exrick XBoot through 3.3.4 can bypass role-based data-scope restrictions and read user records from any department by sending GET /xboot/user/getByDepartmentId/{departmentId} with arbitrary department IDs. The endpoint fails to enforce the data-scope filter, exposing usernames, real names, mobile numbers, emails, and account status (CWE-639 IDOR). The flaw has a moderate CVSS 3.1 score of 5.3 (medium) and requires only a valid session (PR:L, no user interaction); no public exploit code or active exploitation has been identified at time of analysis.
Insecure direct object reference (IDOR) in FastBee through 2.1.0 allows authenticated low-privilege users-including self-registered accounts-to read, overwrite, reassign device associations of, or delete other users' device groups by supplying sequential group IDs, because GroupController queries omit owner/tenant checks. This is a moderate-severity authorization flaw (CVSS 5.3) confined to device-group objects, with no code execution or full account takeover. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV.
Authenticated, low-privileged users of ClickVisual through 1.1.2 can reach ClickHouse instances they were never granted by substituting or incrementing the instance-id parameter in the /api/v2/reports handlers (ReportSourceDatabases, ReportSourceTables, ReportTableColumns, and WhereCheckRun). The handlers in api/internal/api/apiv2/report/report.go fail to confirm that the caller holds a grant on the referenced ClickHouse instance (CWE-862), so any logged-in account can enumerate database and table schemas and infer row counts of restricted tables; the issue is rated 5.3 (CVSS 4.0) and assessed as CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N. Exploitation requires a valid low-privileged account (it is not reachable anonymously), needs no special configuration or user interaction, and is limited to metadata disclosure rather than table contents - no public exploit identified at time of analysis, though a public technical writeup of the flaw is referenced by the CVE.
Cross-tenant data exposure in IoTSharp through 3.6.1 lets any authenticated user read other tenants' customer contact details, device inventories, and device attribute telemetry because the Customers and Devices API handlers fail to scope queries to the caller's tenant (CWE-639, CVSS 5.3). Authentication is trivial to obtain: the anonymous AccountController.Create endpoint allows self-registration, so an attacker only needs a valid GUID belonging to another tenant, and although those GUIDs are random 128-bit values that are not sequentially enumerable, exploitation is realistically targeted rather than mass-enumerable. Impact is read-only and limited to confidentiality - no integrity or availability effect - and the deployment must be genuinely multi-tenant to be exploitable; no public exploit identified at time of analysis, and there is no CISA KEV confirmation of active exploitation.
Missing department-level authorization in PlayEdu through 2.3 lets an authenticated student read course details and download attachment files that belong to departments the student is not entitled to see, because the frontend CourseController skips the department visibility check on those endpoints. The flaw is an IDOR-style (CWE-639) access-control gap: course and attachment identifiers are sequential and therefore enumerable, so a low-privileged account with valid credentials can walk the ID space and harvest course structure and files from other departments. Impact is confidentiality-only - no integrity or availability effect and no escalation to administrative privileges - and the vendor CVSS 4.0 base score of 5.3 (independent assessment CVSS 3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) reflects a medium-severity information-disclosure risk. Exploitation status: no public exploit identified at time of analysis; a public third-party technical write-up of the flaw has been published, and no CISA KEV listing has been associated with this CVE.
Tbed instances through the 20240319 snapshot let any authenticated user rename another user's images by submitting the victim's imgname to the /admin/setImgFileName endpoint, a missing-authorization (CWE-639) flaw that undermines integrity but not confidentiality or availability. Because imgname values are exposed in public image URLs and album listings, the attacker needs no privileged knowledge to target a victim, and the write allows attacker-chosen display text to be attributed to that victim's images (impersonation/defacement). The assessed CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N (scored 5.3 in the source data), requiring a valid low-privilege account but no victim interaction; no public exploit identified at time of analysis.
Authenticated Contributor-level users on a WordPress multisite network running 10up Distributor before 2.3.2 can create draft or published posts on network sites they do not have access to by invoking the dt-push AJAX action with a chosen connection ID and postStatus. The flaw is a moderate-severity missing authorization condition in ajax_push() (CWE-862) and is limited to multisite installations; single-site WordPress installs are not exploitable, and super admins are out of scope. Vendor-released patch: 2.3.2; no public exploit identified at time of analysis.
Unauthenticated content injection in the WordPress NotificationX plugin (WPDevTeam) - versions up to and including 3.3.3 - allows remote attackers to write forged social-proof entries (name, title, message, email, theme) into any enabled non-popup NotificationX campaign by POSTing an arbitrary nx_id to the /notificationx/v1/popup-submit REST route. That route is registered with permission_callback => '__return_true', so no authentication, user interaction, or non-default plugin setting is needed, although exploitation does depend on at least one non-popup campaign (WP Comments, WooCommerce/EDD/Give sales, reviews, etc.) already existing and being enabled on the target site. The impact is confined to the integrity of displayed notification content (CVSS 5.3 Medium - no confidentiality or availability loss), no public exploit code has been identified at time of analysis, and the issue is not flagged as actively exploited.
Missing authorization in Allegro Ralph through 20260902.1 lets any authenticated staff-level user read data-center asset details and manipulate racks through the API. Because RalphPermission skips checks for views that lack a queryset, the DCAssetsView and SRRacksAPIView endpoints at /api/rack/<id> and /api/server_room/<id> are reachable without the rack model permissions they should require, exposing asset hostnames, serials and management IPs and allowing rack creation, modification or movement. No public exploit code has been identified at time of analysis, and the flaw is rated medium severity (CVSS 4.0 base 5.3; independent CVSS 3.1 base 5.3) with risk gated by the need for a valid low-privilege staff credential.
AIHelms 0.1.25 and earlier fails to enforce efficiency:read and efficiency:write authorization in its analytics API, allowing any authenticated low-privileged user to read organization-wide AI spend data and to modify suggestion statuses or generate reports. The exposed routes include /cost/detail, /top-users and /budget in apps/api/v1/efficiency.py, and exploitation requires only a valid low-privilege account - no elevated permissions and no user interaction. Independent assessment rates this a genuine but moderate-priority issue (assessed CVSS 3.1 5.3 with PR:L, C:L/I:L/A:N); no public exploit code or confirmed active exploitation was identified at time of analysis.
Missing authorization in DooTask through 1.9.66 allows authenticated users to read and inject messages into OKR comment dialogs by supplying the dialog_id to msg__list, msg__one, or msg__send* endpoints. The flaw, CWE-639 (IDOR), skips the membership check in WebSocketDialog::checkDialog() for dialogs with group_type 'okr'. Exploitation requires a valid account and knowledge of the target dialog_id; impact is limited to low confidentiality and integrity loss (CVSS 5.3). No public exploit code or active exploitation has been identified.
Stored cross-site scripting in Backdrop CMS Core 1.35.x before 1.35.2 and 1.34.x before 1.34.6 allows an authenticated user holding SVG upload permission to embed dangerous tags or scripting inside an uploaded SVG image, which will execute in a victim's browser only if that SVG is opened directly by its raw file URL. Backdrop's design of embedding all uploaded SVGs inside <img> tags blocks that script during normal page rendering, and reaching the payload requires both the upload privilege (PR:L per the assessed vector) and a victim who navigates to the file itself, so this is a moderate-severity issue (CVSS 5.3, CWE-79) with no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV).
Missing authorization in Ekko Studio through 0.7.36 allows any authenticated user who is not a super_admin to list and clear server-wide login lockouts through the /api/auth/locked-ips endpoint, with a DELETE request lacking an ip parameter invoking the unlockAll() routine. The practical consequence is that the application's login rate limiter can be reset at will, removing the primary obstacle to sustained password guessing against super_admin accounts; the flaw requires a valid low-privileged account (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N, medium severity), so it is most relevant to insider or post-compromise scenarios rather than fully unauthenticated external attack, and it yields no direct account takeover on its own. No public exploit identified at time of analysis (no CISA KEV listing and no exploit code referenced); vendor-supplied fix data is present.
Authenticated users of abp-next-admin 10.2.0 through 10.6.0 who hold the Chat permission can read, and inject messages into, other users' AI chat conversations by supplying a victim's ConversationId GUID to ChatAppService.GetListAsync or SendMessageAsync in the LINGYUN.Abp.AIManagement module. The flaw is a moderate-severity authorization error (CWE-639, IDOR) rather than an unauthenticated remote compromise: exploitation requires a valid account holding the Chat permission (PR:L per the assessed vector) plus knowledge of the target's GUID, which is not readily guessable, so opportunistic abuse is limited. There is confirmed actively exploited status absent (CISA KEV), no public exploit identified at time of analysis, and exploitation is constrained by the out-of-band acquisition of the ConversationId; the advisory and vendor source code are publicly referenced, but that is technical documentation, not weaponized exploit code.
Missing authorization in B3log Solo through 4.4.0 lets an authenticated author account read and act on articles belonging to other authors, because the ArticleConsole handler never enforces per-author ownership checks. The assessed impact is limited confidentiality and integrity loss (CVSS 3.1 5.3, PR:L), and exploitation requires a valid author-level account on a deployment with more than one author, so single-author blogs have nothing to cross-access; the console articles-status endpoint can be queried with the k parameter to probe other authors' drafts, and push2rhy can be used to publish others' articles into the Rhythm community. No public exploit code or confirmed active exploitation was identified at time of analysis, and no vendor-released patched version has been identified.
Missing object-level authorization in MrDoc through 1.1.1 lets any authenticated user publish other users' private drafts, reparent their documents, and inject documents into projects they do not own by supplying arbitrary document or project identifiers to the ImportLocalDoc API. The flaw is a classic insecure direct object reference (CWE-639) assessed at 5.3 (CVSS:4.0 AV:N/AC:L/PR:L/UI:N, low confidentiality and integrity impact) and is confined to the application's own authorization boundary: it cannot reach the host, and it requires a multi-user deployment in which a victim's document or project actually exists. No public exploit code was identified at time of analysis and the CVE is not listed in CISA KEV, though a public technical writeup documents the endpoint's behavior.
Sensitive information exposure in the WordPress plugin Lightweight Cookie Notice (daext) in all versions up to and including 1.19 leaks the W3TC_DYNAMIC_SECURITY constant, which the plugin hardcodes to a publicly known value; a remote, unauthenticated attacker can therefore learn the W3 Total Cache mfunc security key without any credentials or user interaction. On sites that also run W3 Total Cache with its mfunc dynamic-content feature active, knowledge of that key may allow an attacker to forge signed mfunc directives and inject arbitrary PHP code, but the confidentiality leak alone scores only 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) and escalation to code execution is strictly conditional on the co-presence and configuration of that second plugin. No public exploit code has been identified at time of analysis and there is no indication of confirmed active exploitation (no CISA KEV listing).
Missing authorization in Arkon through 0.9.2 lets any authenticated employee who holds only the wiki:read:own_dept permission read another department's wiki metadata - page slugs, titles, node types and link edges up to depth three - by supplying a foreign department slug to GET /api/wiki/graph. Root cause is a CWE-639 user-controlled key flaw: the route passes the caller-supplied slug straight into get_neighborhood() without verifying that the requested department belongs to the requester, so an ordinary employee-level account is sufficient and no elevated role is needed. Impact is deliberately narrow (CVSS 5.3, and our own assessment of CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N): read-only metadata disclosure only, with no page body content, no data modification and no availability impact; no public exploit identified at time of analysis, and exploitation merely requires knowing or guessing a target department slug.
An insecure direct object reference in Fuint through commit 57ec018 lets authenticated members retrieve other members' booking records by supplying arbitrary bookId values to /clientApi/book/myBookDetail. Because bookId is an auto-increment integer, an attacker with a valid member account can enumerate records and obtain contact names, mobile numbers, in-store verification codes, service dates, stores, and remarks. No public exploit identified at time of analysis and no confirmed active exploitation; assessed severity is moderate with low confidentiality impact and no integrity or availability impact.
Exposed debug/diagnostic interfaces in SFM Software Technologies Inc.'s Costifier application let unauthenticated remote attackers reach non-production code paths in production deployments, resulting in limited information disclosure. The flaw carries a medium-severity CVSS 3.1 base score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), meaning no credentials, no user interaction, and no special conditions are needed once the debug interface is network-reachable; integrity and availability are unaffected. All Costifier versions released through 2026-10-16 are in scope, the vendor was contacted but did not respond, and no public exploit identified at time of analysis.
Distributed transaction manipulation in IBM i 7.3, 7.4, 7.5, and 7.6 stems from improper validation of attacker-supplied transaction identifiers, allowing a remote, unauthenticated attacker to alter the state of distributed (two-phase commit / XA-style) transactions that the system participates in. The impact is limited to integrity (CVSS 3.1 base score 3.7, AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N) with no confidentiality or availability effect, and high attack complexity means the attacker must know or predict valid transaction identifiers rather than send arbitrary input. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation; a vendor patch is available, so patched systems are not exploitable.
Insecure direct object reference in WhaTicket Community (all builds through commit cf04795) lets any authenticated agent read another agent's complete WhatsApp ticket history and post replies into that conversation by simply substituting a victim's ticketId in GET /tickets/:ticketId or the /messages/:ticketId endpoints. The flaw is a missing authorization check rather than a memory-safety or injection issue, so it is trivially reachable by any logged-in agent account and requires no user interaction or unusual configuration; the assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) is consistent with the published CVSS 4.0 score of 5.3, placing this at moderate severity rather than critical. No public exploit code was identified at time of analysis and the product does not appear in CISA KEV, although the disclosure is publicly documented in a HackMD writeup and a VulnCheck advisory, which raises the likelihood of opportunistic abuse on internet-exposed instances.
Missing authorization in the Gemini Labs Site Reviews WordPress plugin (versions through 8.3.4) allows unauthenticated remote attackers to perform actions that should require elevated privileges, because affected endpoints do not correctly enforce access-control checks. Per the assessed vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N), exploitation needs no authentication or user interaction against a default install, but impact is limited to low-integrity tampering with plugin-controlled data - no confidentiality or availability effect. No public exploit code and no confirmed active exploitation were identified at time of analysis; realistic risk is constrained to sites that both run the vulnerable plugin version and expose the affected functionality to the network.
Frappe Framework before 15.120.0 and 16.x before 16.33.0 does not enforce its per-user restrict_ip IP allowlist for non-session authentication methods, allowing an authenticated attacker with a valid API key, OAuth token, or header-based credential to authenticate from an IP address outside the configured allowlist. This bypasses network-based access restrictions but requires both a valid non-session credential and a targeted user account that has restrict_ip configured; it is a medium-severity access-control flaw (CVSS 4.0 base 5.3) with limited confidentiality and integrity impact. No public exploit identified at time of analysis.
Open WES through 1.0.0 does not enforce warehouse-scope authorization in GlobalGatewayFilter, so an authenticated user who holds the menu permission for the stock endpoints can freeze or unfreeze container stock belonging to any warehouse by enumerating sequential IDs on the freezeContainerStock and unfreezeContainerStock endpoints. This is a moderate-severity authorization bypass (CWE-639 IDOR; CVSS 5.3) with integrity and availability impact only, and no public exploit identified at time of analysis. Only installations up to and including version 1.0.0 are affected.
Missing authorization in Arkon 0.9.2 and earlier lets an authenticated employee holding only the default skill:read permission read another department's skill version metadata via GET /api/skills/{slug}/versions, exposing version numbers, hashes, storage paths and changelogs that should be scoped to the owning department. The root cause is an omitted can_access_skill check in the list_skill_versions handler, i.e. a CWE-639 authorization bypass through a user-controlled key, and no elevated role, user interaction, or non-default configuration is required beyond knowing or enumerating a target skill slug. Exploitation is limited to existing insiders with a valid account on a multi-department deployment, so single-department or single-tenant installs have no cross-boundary data to leak; no public exploit code was identified at time of analysis and the issue is assessed as a genuine but modest-severity information-disclosure weakness rather than a critical compromise vector.
Arkon deployments through version 0.9.2 allow authenticated, low-privileged employees to read and tamper with other departments' source ingestion records because the by-id routes in app/routers/sources.py (plan, progress, PATCH, retry, approve-extraction) omit the can_access_document authorization check. An attacker with a valid account only needs to know or enumerate a foreign source ID to disclose derived wiki titles and summaries and to change ingestion state; raw source content is not exposed and there is no availability impact. Per the independent assessment this is a moderate authorization-layer (IDOR) flaw requiring PR:L credentials, with no public exploit identified at time of analysis and no CISA KEV listing.
Insecure direct object reference in yshop-crm through 2.1.3 allows an authenticated sales user to read, overwrite, delete, or release into the public pool customer records that belong to other users, simply by enumerating the id parameter on the CRM customer get, update, delete and do-open endpoints. The assessed severity is medium (CVSS 3.1 5.3, vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) because the attacker must already hold a valid sales-privilege account in the admin CRM module; no special configuration or user interaction is required, and every deployment at or below version 2.1.3 with provisioned sales accounts is exposed. No public exploit identified at time of analysis, although a public technical writeup documents the vulnerable endpoints and the associated service-layer code.
Information disclosure in Exrick XBoot through 3.3.4 allows any authenticated user to defeat server-side role data-scope restrictions by appending the parameter openDataFilter=false to the department getByParentId or search endpoints, causing the API to return the entire organization's department tree and names outside the caller's assigned scope. The underlying flaw is an improper-authorization condition (CWE-863) rated medium severity (CVSS 5.3, CVSS:4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L), and the impact is limited to organizational-structure disclosure - no credential exposure, data modification, or availability effect. Exploitation requires a valid logged-in XBoot account whose role carries data-scope restrictions (PR:L); no public exploit code was identified at time of analysis, although a public technical write-up of the bypass and the vulnerable source code are both referenced in the advisory data.
Broken access control in Faveo Helpdesk through 2.0.3 lets any authenticated agent read ticket conversations, customer personally identifiable information, and internal agent notes belonging to other departments by enumerating sequential ticketid values against the GET /ticket/tooltip endpoint (CWE-639, IDOR). The flaw is read-only, requires a low-privileged authenticated agent account (PR:L in the published CVSS vector), and works against default configurations because no special feature toggle or non-default setting is needed; impact scales with how many ticket IDs the attacker can walk. No CISA KEV entry exists for this CVE and there is no confirmed active exploitation, though a public technical writeup documents the attack path; the assigned CVSS score is 5.3.
Authenticated, low-privilege users of Cube-studio through 2026.09.01 can read or clone pipelines belonging to other project groups by enumerating sequential pipeline IDs through the web, log, monitoring, pod, and copy_pipeline endpoints, exposing DAG definitions, Kubernetes cluster names, namespaces, Argo workflow IDs, and pod names. Classified as an authorization bypass through a user-controlled key (CWE-639) and scored CVSS 5.3 (CVSS:4.0 AV:N/AC:L/PR:L/UI:N/VC:L), the issue requires a valid low-privilege account in a multi-tenant deployment where multiple project groups coexist, and its impact is confined to cross-group metadata disclosure and pipeline cloning - no code execution, system compromise, or modification of existing data is enabled. No public exploit identified at time of analysis; risk is highest in shared, multi-tenant installations and negligible in single-group deployments where there is nothing to enumerate.
Missing authorization in REBUILD through 4.5.0 allows any authenticated low-privileged user to read comments and attachment references from tasks in private projects by supplying a valid task ID to the /project/comments/list endpoint, bypassing project membership checks (IDOR, CWE-639). Exploitation requires only a valid account at any privilege level and knowledge of a task ID; the attacker need not be a member of the targeted private project. No public exploit code or confirmed active exploitation was identified at time of analysis, and EPSS data was not provided; impact is limited to confidentiality exposure of task comments and attachment references, with no modification or deletion possible.
Cross-tenant information disclosure in Steedos Platform through 3.0.15-beta.51 allows any authenticated low-privilege user to read other tenants' report definitions by issuing a single GET /api/v1/reports request. The root cause is that the 'reports' object is declared enable_space_global, and objectql's callAdapter skips space (tenant) filtering on find/findOne for such objects, so the API returns report names, descriptions, and object and field API names belonging to other tenants. The exposure is limited to metadata rather than underlying records, the attacker must already hold valid credentials on a genuinely multi-tenant instance, and no public exploit identified at time of analysis; exploitation status is not confirmed actively exploited (CISA KEV).
BeikeShop through 2.0.0.31 contains an insecure direct object reference (IDOR) in the markAsShipped handler of RmaController that allows authenticated customers to modify other customers' return shipping details. By submitting sequential RMA IDs to the account/rmas/{id}/mark_as_shipped endpoint, an attacker with a valid customer account can overwrite courier names and tracking numbers and mark approved returns as shipped. The vendor CVSS 4.0 base score is 5.3 (PR:L, VI:L), matching an independent assessment of CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N; no public exploit code has been identified at the time of analysis, though a technical write-up is available.
Cross-tenant insecure direct object reference in ChatWiki 2.9.6 and earlier allows any authenticated tenant user to read another tenant's form filter rules and overwrite that tenant's filter sort order by supplying arbitrary or sequential form_id values to the form-filter management endpoints getFormFilterList, getFormFilterInfo and updateFormFilterSort. Exploitation requires a valid low-privilege ChatWiki account on a multi-tenant deployment (PR:L in the assessed vector), so the flaw is not reachable pre-authentication, and the impact is confined to form-filter configuration data rather than code execution or administrative takeover. No public exploit code identified at time of analysis, though a detailed third-party technical writeup and the vulnerable source code are publicly linked in the advisory references.
An insecure direct object reference (IDOR) in PickMall lilishop through 5.0.0 allows authenticated buyers to read other buyers' invoice records-including invoice titles, taxpayer identification numbers, order numbers, member IDs and member names-by supplying another buyer's receipt ID to GET /buyer/trade/receipt/{id}. The flaw resides in ReceiptServiceImpl.getDetail, which performs no ownership check, and can only be exploited by a user with a valid buyer account who can guess or enumerate valid receipt IDs. This is a moderate-severity information-disclosure issue (CVSS 5.3, CWE-639); it is not listed in CISA KEV and no public exploit code or active in-the-wild exploitation has been confirmed, though a public technical writeup exists.
Authenticated API users of Aureus ERP through 1.6.0 can create new records or move existing ones into companies they are not entitled to by submitting a foreign company_id to plugin REST endpoints, breaking the multi-company data segregation that the ERP relies on. The flaw is an IDOR/authorization bypass (CWE-639) in the Laravel Form Request validation of partners, sales, inventories, and accounts handlers, which checked only that the supplied company_id existed and never that it belonged to the caller's allowed companies; it is exploitable only by an authenticated account with API access and only on deployments that actually use more than one company. Rated 5.3 (CVSS 4.0) and independently assessed as CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N, its real-world priority is moderate-to-low, patch code is available upstream, and no public exploit was identified at time of analysis.
Missing authorization in the 10up Distributor WordPress plugin before 2.3.2 allows authenticated users with Contributor-level privileges to invoke AJAX handlers that were intended only for administrators, enabling them to send stored external-connection credentials to an attacker-controlled server via dt_verify_external_connection or to create new external connections via dt_begin_authorization. Exploitation requires a valid low-privilege login (CVSS vector PR:L, so authenticated, not anonymous), and the credential-theft path only works on sites that already have a configured external connection holding stored credentials; sites without pre-existing connections or without untrusted Contributor-level accounts have no exposed attack surface. No public exploit has been identified at time of analysis, and the vendor has released a fix in version 2.3.2.