Missing authorization in the Arraytics WP Event Solution WordPress plugin (all versions through 4.1.25) allows remote attackers to invoke functionality that should be restricted to privileged users, with the CVSS vector AV:N/AC:L/PR:N/UI:N indicating no authentication, no user interaction, and no non-default configuration are needed against a site that has the plugin installed and active. Impact is limited to integrity (C:N/I:L/A:N), so affected installations face unauthorized modification or creation of plugin-managed content rather than data disclosure or denial of service. The issue is rated moderate (CVSS 5.3) and no public exploit code has been identified at time of analysis.
Missing authorization checks in the Fluent Forms Pro Add On Pack for WordPress, affecting versions up to and including 6.2.13, allow unauthenticated remote attackers to reach functionality that should require elevated permissions, yielding a low-integrity impact (vendor/NVD CVSS 3.1 base score 5.3, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N). Because the vector is PR:N/UI:N, no login and no victim interaction are required; the practical exposure is limited to incorrect modification of plugin-controlled data, with no confidentiality or availability impact assessed. Only sites that have purchased and activated this paid add-on are affected - installations running the free Fluent Forms base plugin alone are not vulnerable. At time of analysis there is no CISA KEV entry and no public exploit identified, and no EPSS score was supplied.
Reflected cross-site scripting and an open redirect in the front-end "share mini page" of the Joomla Event Gallery extension (svenbluege.de) affect all versions below 6.6.0. When the "Share article links" option is enabled, the article address carried in a crafted share link is rendered into the page without validation or output encoding, and when the link type is set to "Image Page with Redirect" the address is followed immediately, allowing an attacker to execute script in the browser session of any visitor who opens the prepared link or to silently redirect that visitor to an attacker-controlled site. The vulnerability is unauthenticated remote (CVSS 4.0 base 5.3; independently assessed as CVSS 3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N), requires a victim to click the malicious link, and no public exploit code has been identified at time of analysis; there is no server-side read or write, so impact is confined to the victim's browser session.
Information disclosure and broken authorization in Penpot before 2.18.0 allow an unauthenticated caller who holds any valid share link to the get-view-only-bundle RPC to retrieve all share-link rows for the same file, including secret IDs and page, comment, and inspect scopes. The issue is rated CVSS 5.3 (CWE-862) and is fixed in 2.18.0; no public exploit code was identified at time of analysis, and exploitation requires possession of a share-link URL plus multiple differently scoped links on the same file to yield additional access.
Improper handling of grouping query fields in Plane (the open-source project management tool) versions prior to 1.4.0 allows an unauthenticated remote attacker to send arbitrary ORM field names through the public issues endpoint's group_by and sub_group_by parameters, producing unhandled FieldError/KeyError conditions and repeated HTTP 500 responses, or using the resulting error behaviour as a blind relational-traversal oracle. The vulnerable path is the publicly published Spaces endpoint, so only deployments that expose that endpoint over the network are reachable; no credentials or user interaction are required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, 5.3, CWE-943), and the confirmed impact is limited to availability/error-oracle exposure rather than direct column-value disclosure. The flaw is not listed in CISA KEV and no EPSS score was provided; the vendor advisory contains a proof-of-concept request (group_by=state_id&sub_group_by=created_by__password) demonstrating the parameter combination, so publicly available exploit demonstration code exists, and the issue is fixed in Plane 1.4.0.
HeYm (heymrun/heym) deployments prior to v0.0.112 can be tricked into emailing human-in-the-loop (HITL) review links that point to an attacker-controlled domain, leaking the capability tokens embedded in those links. An unauthenticated attacker who can trigger anonymous workflows and who supplies a forged Origin or X-Forwarded-Host header causes build_public_base_url() to derive the notification base URL from attacker input; if a legitimate reviewer then clicks the link, the token is captured and can be replayed to submit review decisions that the platform executes with the workflow owner's credentials. Rated medium severity (CVSS 4.0 base 5.3; independently assessed as CVSS 3.1 AV:N/AC:L/PR:N/UI:R with low confidentiality and integrity impact), the flaw is conditional - it requires an anonymously triggerable workflow, the HITL feature, and reviewer interaction - and no public exploit code or confirmed active exploitation was identified at time of analysis. The vendor-released fix is Heym v0.0.112.
Arbitrary file write in Perforce P4 Search versions prior to 2026.4.2 allows an attacker who already holds super-user or service-token privileges to write files with attacker-controlled content into the P4 Search installation directory via the extension installation feature, which fails to validate supplied file names (CWE-73). The vulnerability is authenticated and gated by a PR:H requirement, so exploitation is not possible for unauthenticated or low-privileged users; the realistic risk is confined to malicious insiders, abused service tokens, or an attacker who has already compromised a privileged account. The vendor rates it CVSS 4.0 base 5.1 (VC:N/VI:L/VA:L), and no public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis.
Server-side request forgery (SSRF) in Shaarli up to 0.16.3 allows an attacker who can reach the admin-only MetadataController endpoint to make the server fetch arbitrary HTTP(S) URLs, including those resolving to private, loopback, link-local, or reserved addresses. Exploitation requires either an authenticated administrator session (PR:H) or tricking a logged-in admin into triggering the request, which was feasible before the fix because the endpoint did not validate a CSRF token; the pre-patch code also only checked that the URL scheme contained the substring 'http' and performed no IP validation. There is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis; a vendor patch is available in version 0.16.4.
Stored cross-site scripting in the LearnPress WordPress plugin through version 4.4.9.1 allows authenticated users holding the Instructor role to inject JavaScript into quiz question hint and explanation fields through the update_question AJAX handler, where the payload is persisted and later rendered in the browser session of every student who opens the affected quiz. The root cause is missing sanitization (CWE-79) of those two fields before storage and output, which the upstream commit addresses with Template::sanitize_html_content. Exploitation is limited: it requires an Instructor-level account plus a student actually viewing the quiz, yields only script execution in the student's browser (no server compromise, no privilege escalation), and no public exploit code was identified at time of analysis; this is a genuine but moderate-severity issue rather than a drop-everything priority.
The Host search feature in the Zabbix Frontend allows filtering on fields that are never displayed in search results, including stored IPMI credentials and PSK values, so an authenticated user with read access to hosts can submit a guessed secret and infer from whether results are returned whether the guess was correct. This is a guess-confirmation oracle rather than a direct credential readout: each request leaks only one bit of information, so short or weak IPMI passwords are realistically recoverable through repeated queries, while high-entropy PSK secrets may be impractical to brute-force. Successful abuse yields low-confidentiality impact and requires the attacker to already hold a valid low-privileged frontend account (PR:L, authenticated per the CVSS vectors); no public exploit code or confirmed active exploitation has been identified at time of analysis.
DYMO ID 1.5.1.71 and earlier automatically parse job files with DTD processing enabled, allowing a crafted file placed on a browsed network share to trigger XML external entity (XXE) processing. This can lead to SSRF, NTLMv2 credential capture, local file disclosure, or process crash, though the independent assessment notes impact is bounded and does not include arbitrary code execution. No public exploit code has been identified at time of analysis, and the vendor released a fix in version 1.6.0.
Cross-site request forgery in the Event Gallery extension for Joomla (all versions before 6.6.0) allows an attacker-controlled external page to silently flip back-end configuration flags - default payment method, shipping method, image type set, order status, watermark, putting an event in or out of the shop, selecting an event's main image, toggling the main-image-only flag, and sorting event images - in the name of an administrator. The eight affected back-end list buttons never validate the Joomla form token, so the forged requests execute with the privileges of a victim who has an active administrator session and visits the malicious page (user interaction required, per the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N). Impact is deliberately narrow - no data can be read or deleted and orders are unaffected - so this is a medium/low-priority issue rather than a high-CVSS alarm; no public exploit code or confirmed active exploitation was identified at time of analysis, and the flaw is fixed in version 6.6.0.
Theme translation-file path traversal in Ghost CMS lets an authenticated Administrator read JSON files outside the active theme's directory, potentially exposing server configuration secrets such as database credentials or API keys stored in JSON. All Ghost releases from 1.20.0 up to but not including 6.64.0 are affected, with the fix shipped in 6.64.0; because exploitation requires the highest-privilege Administrator role (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N, base 4.9) and yields confidentiality-only impact, this is a low-to-moderate priority issue rather than an anonymous remote attack. No public exploit code has been identified at time of analysis.
A denial-of-service condition in Ghost CMS affects versions 4.0.0 through 6.66.x, where a crafted content import file can drive catastrophic regular-expression backtracking and pin the Node.js event loop, leaving the server unresponsive. The vulnerability is only reachable by an authenticated Ghost Administrator (CVSS PR:H) who submits a malicious import through the built-in content import feature, so the practical risk is limited to environments where admin credentials are already compromised or misused. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (no CISA KEV listing); vendor-released patch: 6.67.0.
Denial of service in Ghost CMS 5.37.0 through 6.66.x allows an authenticated administrator to pin server CPU and render the Ghost instance unresponsive by sending a crafted request to the external media inliner, which compiles attacker-influenced domain strings into unescaped regular expressions (CWE-1333, inefficient regular expression complexity / catastrophic backtracking). Exploitation requires a Ghost Administrator account (CVSS PR:H, AV:N/AC:L/UI:N/S:U/C:N/I:N/A:H, base score 4.9), so realistic risk is confined to malicious or compromised admin accounts rather than anonymous visitors or the read-only front end. No public exploit identified at time of analysis; the vendor fix is contained in Ghost 6.67.0.
Penpot versions prior to 2.18.0 fail to protect a team owner from removal by another administrator: a non-owner team admin can call the delete-team-member RPC to strip the owner's team-profile membership, locking the owner out of the team and its projects, files, fonts, and media. The flaw is an authenticated, high-privilege availability issue (CVSS 4.9, AV:N/PR:H, availability-only), not a remotely exploitable unauthenticated attack, and no public exploit code was identified at time of analysis. The issue is fixed in 2.18.0.
Cross-tenant event-stream disclosure in Rapid7 Velociraptor lets an authenticated API user who holds event-watching privileges in one organization read WatchEvent gRPC streams belonging to a different organization they are not authorized for, because the server validates permissions against the caller's own OrgId instead of the OrgId supplied in the request. Only multi-org (multi-tenant) deployments with more than one Org defined are meaningfully exposed; single-org installs have no other tenant to pivot to, and the impact is confidentiality-only with no write or denial-of-service effect. Exploitation requires valid low-privileged API credentials (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), and no public exploit code was identified at time of analysis.
Joplin Server releases prior to 3.7.2 store CSRF, account-confirmation, email-change and password-reset tokens in a single purpose-less pool, so an unauthenticated remote attacker who already holds any one of a victim's tokens can submit it to the public password-reset endpoint and set a new password for that account, simultaneously deleting the victim's existing sessions and API applications. The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N, 4.8; independent assessment also credits A:L) reflects that exploitation is remote and needs no authentication, but is gated on a hard prerequisite: the attacker must obtain the victim's token through an entirely separate disclosure channel, because the vulnerability itself does not leak it. This is a CWE-620 unverified password change (token-purpose confusion) rather than a self-contained takeover path, it is not listed in CISA KEV, and no public exploit code was identified at time of analysis; the vendor has released an exact fix in Joplin Server 3.7.2.
CSS injection in Joplin Desktop versions prior to 3.7.13 allows a malicious note containing a jsoncanvas fence to inject styles and remote CSS imports into the application chrome when the victim selects the note in the Whiteboard editor, enabling UI redressing, open-signaling, and possible disclosure of exposed attribute values. Content Security Policy blocks inline script execution, so the supported impact is not code execution, and no public exploit has been identified at time of analysis. Vendor-released patch: 3.7.13.
Processing a crafted document with Docling (or the docling-slim distribution) versions 2.45.0 through 2.130.x can exhaust process memory: a small gzip-compressed tar archive that declares a very large number of empty members causes the full archive member list to be materialised before the configured max_member_count limit can stop processing. The flaw sits in METS-GBS format detection (docling/datamodel/document.py) and the METS-GBS backend (docling/backend/mets_gbs_backend.py), and because detection runs before the allowed_formats restriction is applied, an attacker does not need METS-GBS to be an enabled format - remote, unauthenticated delivery is possible per the CVSS vector (AV:N/PR:N), though a user or automated pipeline must actually submit the file (UI:R), and the resulting impact is limited to availability (A:L, CVSS 4.3) with no code execution or data disclosure. No public exploit code was identified at time of analysis and the issue is not recorded as actively exploited; a vendor fix is available in 2.131.0.
Information disclosure in Docling (and the docling-slim distribution) versions 2.16.0 through 2.130.x lets an attacker embed local file paths or file: URIs inside a crafted DoclingDocument JSON that, when re-converted and enriched or exported with ImageRefMode.EMBEDDED, causes Docling to open and embed the referenced file's bytes into Markdown or HTML output. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N, score 4.3), no privileges are needed but the victim must actively load the malicious JSON, and exposure is constrained to files Pillow can decode as images, with differing decode behavior potentially revealing whether a path exists. There is no public exploit code identified at time of analysis and the issue is not listed in CISA KEV; the flaw is fixed in Docling 2.131.0.
WordPress sites running the Memberful - Membership Plugin (memberful-wp) through version 1.81.2 can expose sensitive system information to any authenticated user holding a low-privilege account, such as a subscriber or registered member. The flaw is reachable over the network with low attack complexity and requires no user interaction, but the impact is confidentiality-only and limited in scope (CVSS 4.3, C:L), making this a low-to-moderate priority hardening item rather than an emergency patch. No public exploit code was identified at time of analysis, and the vulnerability is not known to be actively exploited.
Authenticated low-privileged users can read support tickets belonging to other users in the Ahmad JS Help Desk WordPress plugin through version 4.0.0 by manipulating user-controlled object references. This is a classic insecure direct object reference (IDOR, CWE-639) limited to confidentiality impact; authentication is required per the CVSS vector (PR:L), and no public exploit code has been identified at time of analysis. With a CVSS score of 4.3 and no active exploitation reported, this is a moderate-severity, low-priority issue.
Plane prior to 1.4.0 leaks cycle and module metadata from private projects to any authenticated member of the same workspace, because the WorkspaceCyclesEndpoint and WorkspaceModulesEndpoint filter results only by workspace__slug rather than by project membership. A low-privileged user such as a Guest with access to a single project can enumerate cycle and module names, descriptions, sprint dates, issue counts, progress snapshots, external integration IDs, linked URLs, and member lists belonging to projects they were never added to. The issue is fixed in 1.4.0 via upstream commit b3591b9e; there is no public exploit identified at time of analysis, and the assessed CVSS is 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), reflecting an authenticated, read-only confidentiality impact.
Authenticated staff holding the Editor or Super Editor role in Ghost CMS versions 0.5.0 through 6.63.x can escalate the privileges of Author and Contributor accounts by assigning their own Editor role to those users through the Ghost Admin API, even though they lack permission to grant that role. The flaw is bounded - attackers can only confer their own Editor-level role and cannot push targets to Administrator or Owner - and exploitation requires an existing, trusted staff account rather than outsider access. No public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), but the vendor released a fix in version 6.64.0, so unpatched, multi-role Ghost publications should upgrade promptly.
Missing authorization checks in the WordPress Event Tickets plugin from Liquid Web / StellarWP (versions through 5.30.0) allow an authenticated low-privilege user to carry out restricted ticket-related actions they should not be permitted to perform, resulting in limited integrity impact with no data disclosure or denial of service. As confirmed by the CVSS vector (PR:L), exploitation requires a valid account on the target site at a low privilege level - typically a self-registered subscriber, customer, or event attendee - so sites that allow open user registration carry more exposure than those with registration closed. No public exploit code has been identified at time of analysis and the issue is not reported as actively exploited; the assessed severity is low (CVSS 4.3), making this a genuine-but-low-priority hardening item rather than an emergency patch.
Information disclosure in the WP SYNTEX Polylang WordPress plugin through 3.8.7 lets an authenticated low-privileged user bypass a missing authorization check (CWE-862) and retrieve embedded sensitive data they are not entitled to access. The issue carries a CVSS 3.1 base score of 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N): exploitation is network-reachable, low complexity and needs no user interaction, but requires a valid account with at least low privileges such as a default Subscriber, with no impact to integrity or availability. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (not in CISA KEV), so exposure is materially higher on sites that permit open user registration or host many low-trust accounts than on sites with restricted account creation.
Missing authorization checks in the WordPress plugin WP Admin Audit (Brandtoss) through version 1.2.17 let an already-authenticated low-privilege user reach plugin functionality and audit data they are not permitted to see. Per the assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) the attacker must hold a valid account on the target site, so the flaw is not anonymously exploitable, and the impact is limited to confidentiality with no integrity or availability effect. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; severity is moderate (vendor-reported 4.3), with the main risk being disclosure of audit-log information to subscribers or other low-privilege accounts.
Missing authorization checks in the WordPress plugin WP Dummy Content Generator (all versions through 4.0.0) let an authenticated low-privilege user - a subscriber or contributor, per the CVSS vector's PR:L - invoke plugin functionality that should be reserved for higher-privileged roles, producing a limited integrity impact (CVSS 3.1 score of 4.3, vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, CWE-862). Exploitation requires the plugin to be installed and active and the attacker to hold valid credentials for a registrable low-privilege account, with no user interaction needed, and the effect is confined to modification of content the plugin manages rather than disclosure or denial of service. There is no public exploit identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing); no EPSS score was supplied in the source data, so the residual risk is low-to-moderate and is highest on sites that permit open self-registration.
Information disclosure in Penpot prior to 2.18.0 lets a holder of a page-scoped share link pull comment threads and full comment bodies from pages they were never granted access to within the same file, exposing commenter names, email addresses, profile photos, and internal page identifiers; those leaked page IDs can then be chained with other page-reading functionality to reach unshared design content. The flaw sits in the get-comment-threads, get-comment-thread, and get-comments RPC commands, which called the comment permission check but never enforced the share link's :pages restriction; exploitation requires an authenticated party (CVSS PR:L) who already possesses a valid page-scoped share link, so it is not anonymous access to arbitrary files. Risk is moderate and confidentiality-only (CWE-200, CVSS 4.3), there is no public exploit identified at time of analysis and no CISA KEV listing, and the issue is fully remediated in Penpot 2.18.0, so instances on 2.18.0 or later are not affected.
Authenticated cross-workspace issue linking in Plane versions prior to 1.4.0 lets a user who holds a valid account in any workspace attach issues belonging to a different workspace to modules, cycles, relations, or sub-issues inside their own workspace by passing foreign issue UUIDs in the URL path. The flaw is an object-reference authorization gap (CWE-639) scored CVSS 4.3 with integrity-only impact (I:L, C:N, A:N); it requires knowledge of a specific victim issue UUID, which Plane generates as a non-enumerable 128-bit identifier, making practical exploitation opportunistic rather than broad. No public exploit code has been identified at time of analysis, and CISA KEV does not list this CVE; a vendor-released patch exists in Plane 1.4.0.
Cross-site scripting in Red Hat Quay 3 lets an unauthenticated remote attacker execute arbitrary script in a victim's authenticated browser session by tricking the user into completing login through a crafted URL, because the application does not validate the post-login redirect destination before navigating. Exploitation is tightly constrained: the deployment must be configured with direct database authentication (installs delegating to OIDC/LDAP/SSO are unaffected) and the victim must both click the malicious login link and finish authenticating through it. Severity is low-to-moderate (CVSS 4.2, AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N), impact is confined to the victim's own session, and no public exploit identified at time of analysis.
vLLM versions prior to 0.30.0 derive the flash late-interaction query-cache key from the caller-controlled X-Request-Id header, so an authenticated API caller on a shared deployment can collide with a victim's in-flight request and cause the victim's documents to be scored against the attacker's query through the /score and /rerank endpoints, while shared use counters can also give rise to a late-interaction cache-miss error. The assessed vector is CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L (base 4.2), reflecting a narrow concurrency race that requires knowledge of or a lucky guess at the victim's request identifier, and no confidentiality impact; there is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV). The issue is fixed in vLLM 0.30.0, and the practical risk is confined to multi-tenant or otherwise shared deployments that actually enable the flash late-interaction scoring path.
Server-side request forgery (SSRF) in Ghost CMS versions 6.0.9 through 6.64.x lets an unauthenticated remote attacker induce the server to issue limited HTTP requests to hosts on its internal network. The flaw is blind - no response body is ever returned to the attacker - so the practical value is confined to request-triggered side effects and liveness/timing inference rather than data exfiltration, and exploitation depends on the target deployment actually having reachable internal hosts (e.g. NAT64/DNS64 setups or flat internal networks). The vendor fixed the issue in Ghost 6.65.0; no public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV, consistent with the assessed CVSS 3.1 score of 4.0 (AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N).
Blind server-side request forgery (SSRF) in Ghost CMS versions 6.54.1 through 6.64.x lets an unauthenticated remote attacker coerce the server into issuing limited HTTP requests to hosts on its internal network, using functionality such as the Webmentions feature to submit attacker-controlled URLs that are later fetched by Ghost's oembed/bookmark/favicon pipeline. The impact is constrained: no response body is returned to the attacker, so the attack yields only internal-host reachability probing rather than data exfiltration, and exploitation depends on winning a DNS-rebinding race (AC:H per the assessed vector, overall CVSS 4.0). No public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation; the vendor-released patch is Ghost 6.65.0.
Ghost CMS versions 6.14.0 through before 6.27.0 allow an authenticated staff-level user to read files outside the configured local storage directory through a path traversal issue in the default LocalStorageBase storage adapter. The issue is authentication-gated and low severity, requires an existing staff account created by an administrator, and no public exploit identified at time of analysis; the vendor fixed it in Ghost 6.27.0.
Archive extraction in GnuPG's gpgtar tool (all versions before 2.5.19) can write outside the intended output path: when a user extracts an untrusted archive with the --directory (-C) option into an already-existing, non-empty directory that contains or resolves through a pre-existing symlink, gpgtar follows that link and creates or overwrites a file elsewhere on the filesystem. Exploitation demands substantial victim-side prerequisites - local delivery of a malicious archive, an active extraction the victim must perform, and a target directory that is both non-empty and already symlink-exposed - so the assessed impact is limited to low-integrity and low-availability effects (CVSS 3.1 score 3.6, AV:L/AC:H/PR:N/UI:R), bounded by the extracting user's own filesystem permissions; extraction into a fresh empty directory is expressly not affected. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV.
Front-end request desynchronization in Progress Telerik Fiddler Classic for Windows (versions prior to v6.0.20262.10021) allows a locally positioned, low-privileged actor to send a single malformed request through the proxy's forwarding component and have it split into two requests delivered to the origin server, returning an extra smuggled response on the reused client connection. Exploitation is constrained: it requires local access to the Fiddler proxy (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N, base 3.6), depends on the exact condition of a request carrying both Content-Length and Transfer-Encoding headers combined with connection reuse and pipelining behavior, and is limited to shared or multi-user developer environments rather than production edge deployments. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (not in CISA KEV); the vendor-released fix is v6.0.20262.10021.
An out-of-bounds read in Android's camera3 stream splitter (DeprecatedCamera3StreamSplitter.cpp, returnOutputBufferLocked) lets a locally installed, low-privileged application read a small amount of adjacent process memory while camera output buffers are being returned, potentially disclosing limited information on Android 14, 15, 16, 16-qpr2, and 17. The flaw is a missing bounds check reachable only from local code already running on the device (CVSS 3.1 base 3.3, AV:L/PR:L/UI:N, C:L/I:N/A:N), and no public exploit identified at time of analysis, with SSVC assessing exploitation as 'none' and not automatable. The issue is fixed in the October 2026 Android Security Bulletin (2026-10-01) patch level, and this is a genuinely low-severity, low-priority issue despite being in the ubiquitous Android platform.
Any authenticated staff-level user on a self-hosted Ghost instance running versions 0.7.2 through 6.63.x could infer the relative ordering of other staff users' hashed password values through admin API query options, a low-severity side-channel disclosed as CWE-203 (Observable Discrepancy). The exposure is limited: raw hashes and passwords are never returned, and turning ordering metadata into a usable credential requires substantial additional effort, which is reflected in the CVSS:3.1 base score of 3.1 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N) - a trusted staff account is a prerequisite, attack complexity is high, and only low confidentiality impact is assessed. There is no public exploit identified at time of analysis and no indication of active exploitation; the issue is fixed in Ghost 6.64.0 via the upstream PR and commit referenced in the advisory.
Unlimited credential-guessing against the linlinjava litemall admin login endpoint is possible because the application imposes no lockout, throttling, CAPTCHA, or failed-attempt limit on the AdminAuthController in the litemall-admin-api module (CWE-307), affecting versions up to and including 1.8.0. A remote, unauthenticated attacker (CVSS 4.0 vector PR:N) can repeatedly submit password guesses, but exploitation is rated difficult and high-complexity: the flaw only removes the brute-force barrier rather than bypassing authentication, so it still depends on weak, default, or guessable admin credentials and on the admin-api component being deployed and network-reachable. Publicly available exploit code exists, and the vendor has not responded to the issue report; impact is confined to low confidentiality with no integrity or availability effect, making this a genuinely low-priority issue despite the public documentation.
Server-side request forgery in the Ghost CMS webhooks feature (versions 1.18.0 through releases prior to 6.27.0) allows an authenticated staff user who can create or edit webhooks to point a webhook target_url at internal hosts and force the Ghost server to issue requests to them. The CVSS vector (AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N, score 2.7) confirms this is a network-reachable but privileged-account-required issue whose impact is limited to low confidentiality loss - blind or semi-blind probing rather than response retrieval or code execution - and there is no public exploit identified at time of analysis. Ghost 6.27.0 fixes the issue by routing webhook delivery through a request library that blocks internal IPs unless the operator explicitly opts in via a new configuration flag.
Argument injection in the OpenPrinting CUPS mailto notifier can let a low-privileged user or authorized subscription creator influence the configured sendmail command when CUPS email notifications are enabled. Exploitation requires a crafted notify-recipient-uri beginning with '-' and an MTA that interprets it as an option; the assessed risk is low because email notification is non-default, CUPS is typically local-only (AV:L), complexity is high, and impact is limited to low confidentiality and integrity in the assessed vector. No public exploit identified at time of analysis. Affected deployments include upstream OpenPrinting CUPS and CUPS in Red Hat Enterprise Linux 8, 9, 10, and Red Hat Hardened Images.
Use-after-free in the TXTP file handler of vgmstream (the open-source video-game audio decoding library) affects builds up to and including revision r2117, specifically the make_group_random function in src/meta/txtp_process.c. The flaw is triggered when a locally processed TXTP playlist file uses a random group definition, causing a stale VGMSTREAM pointer to be dereferenced after the group structure is rebuilt; the vendor rates it CVSS 4.0 2.4 (AV:L/PR:L/UI:P), and the independent assessment agrees on local-only, user-interaction-gated reachability with limited impact (C:L/I:L/A:L), making a crash/denial-of-service the most plausible outcome rather than code execution. There is no CISA KEV entry and no public exploit identified at time of analysis. An upstream fix exists as commit ae37662ad626254ddd96ad69ac263792d7a92024.
Zabbix Server and Proxy can be crashed by a crafted binary item value containing a NULL byte, causing loss of monitoring availability on deployments that use MySQL or MariaDB as the Zabbix backend database. Exploitation is not anonymous: the CVSS vector (PR:L) indicates an authenticated, low-privileged user able to submit binary item values is required, and the attack additionally depends on a specific input condition (AT:P), which is why the vendor-assigned severity is low (CVSS 4.0 base 2.3) and our independent assessment matches at CVSS 3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L. No public exploit code has been identified and the issue is not listed as confirmed actively exploited (CISA KEV); impact is confined to availability, with no confirmed data exposure, integrity loss, or code execution.
Request forgery in MongoDB Controllers for Kubernetes allows an authenticated user who can modify an OpsManager custom resource to cause unintended administrative changes in Enterprise Ops Manager when backup reconciliation is enabled. The flaw involves insufficient escaping of Ops Manager backup store identifiers when the controller builds admin API request paths. It is a low-severity issue with no public exploit identified at time of analysis, and the vendor fixed it in MongoDB Controllers for Kubernetes 1.13.0.
Trailing-slash directory redirects emitted by Chainguard Academy's nginx configuration downgrade clients to plaintext HTTP, because the redirect is built from the $scheme variable and TLS terminates at the Cloud Run load balancer in front of Nginx, making $scheme evaluate to "http". An attacker who already holds an on-path (MITM) network position can therefore read or modify documentation content delivered to a victim who requests a slashless directory path over HTTPS, but only when the client does not enforce HSTS - command-line HTTP clients and scripts that follow redirects are affected, while HSTS-preload browsers are not, since the .dev top-level domain is on the preload list. This is a low-severity issue (CVSS 4.0 base 2.3; independently assessed as CVSS 3.1 AV:N/AC:H/PR:N/UI:R with low integrity impact only), and no public exploit was identified at time of analysis.
Reflected cross-site scripting in feelcrm-os 1.0.0 lets remote attackers execute arbitrary script in a victim's browser by crafting a URL whose redirect_url argument is rendered unsanitized by IndexController::index in App/ThinkPHP/Common/functions.php. Exploitation requires no authentication of the attacker (CVSS PR:N in both the vendor and independent vectors) but does require victim interaction - a user must open the attacker-supplied link, which sharply limits mass exploitation, and impact is integrity-only on the client side with no server-side confidentiality or availability loss. Publicly available exploit code exists and the issue was reported to the maintainers via GitHub issue #2, but the project has not responded; no vendor-released patch or KEV listing is identified at time of analysis, and EPSS or KEV corroboration is absent.
Mass assignment in Jeebase 0.0.1 allows an authenticated remote attacker to inject unintended object attributes through the updateUser function of UserService, reachable at /user/update/info via the user/tempUser parameter. The flaw (CWE-913) lets an attacker set properties on the bound object beyond intended profile fields, producing low-impact data manipulation or information disclosure, and publicly available exploit code exists. The vendor has not responded to the issue report and no official patch is available at time of analysis; the assessed CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L, making this a low-priority, high-noise finding typical of small-project disclosures.
An authenticated low-privilege user of a dotnet eShop (.NET 8) deployment can read order records belonging to other customers by manipulating the OrderNumber argument accepted by the GetOrderAsync function in the Ordering API (src/Ordering.API/Apis/OrdersApi.cs). The flaw is an improper control of resource identifiers issue (CWE-99) tagged as Information Disclosure and scored only 2.1 by the CNA (CVSS 4.0 vector), with our independent assessment at CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N - confidentiality-only impact with no code execution or data modification. Exploitation requires a valid account (PR:L), no CISA KEV evidence of active exploitation is present, and no vendor-released patch has been identified because the maintainers have not yet responded to the report (GitHub issue #996); note that the CNA's CVSS 4.0 vector marks exploit maturity as E:P, indicating publicly available exploit code exists, but that eShop is a Microsoft reference sample application rarely run in production, which keeps realistic risk low.