CVE Vulnerability Catalog

Wallos is an open-source, self-hostable personal subscription tracker. From version 4.0.0 to before version 4.9.6, Wallos's OIDC login links an incoming OIDC identity to an existing local account by matching the email claim alone, without verifying that the IdP marked that email as verified (email_verified). When Wallos is configured against an IdP that lets a user present an arbitrary or unverified email (multi-tenant IdPs, IdPs with open self-registration, or any IdP the attacker partly controls), an attacker with no Wallos account can authenticate with the admin's email and be logged in as the admin — full account takeover, no password needed. This issue has been patched in version 4.9.6.

Wallos is an open-source, self-hostable personal subscription tracker. Prior to version 4.9.6, Admin-configured OIDC token_url and user_info_url in includes/oidc/handle_oidc_callback.php:18-49 are used directly in curl_init() with zero SSRF filtering. Unlike logo/webhook URLs which have validate_webhook_url_for_ssrf(), OIDC URLs bypass all protections. Admin sets URL to http://169.254.169.254/latest/meta-data/ for cloud metadata access or internal network pivoting. This issue has been patched in version 4.9.6.

Wallos before version 4.9.6 contains a path traversal vulnerability in the POST /endpoints/db/restore.php endpoint. The ZipArchive::extractTo() function does not validate entry names for '../' sequences, allowing an admin to upload a crafted zip with logos/../../endpoints/shell.php to write a webshell to the webroot. The extension filter only applies to the post-extraction logo copy step, so it does not prevent this attack.

Wallos before version 4.9.6 contains an SSRF vulnerability in the POST /endpoints/notifications/testemailnotifications.php endpoint. The smtpaddress and smtpport parameters are taken from the POST body with zero SSRF validation, and PHPMailer connects to the attacker-supplied host:port. Every other notification endpoint uses ssrf_helper.php but email was missed. Any authenticated user can probe internal network and access cloud metadata.

Wallos before version 4.9.4 has an authentication bypass vulnerability in the endpoints/db/import.php endpoint. The only guard is a user-table row count – if zero (fresh/unconfigured install), an unauthenticated attacker can replace the entire database.

Wallos before version 4.9.4 has a vulnerability in the OIDC mechanism. login.php generates an OIDC state nonce stored in $_SESSION['oidc_state'], but checksession.php dispatches the OIDC callback without comparing the incoming state against the session value. An attacker can trick a victim into visiting a crafted URL, causing Wallos to exchange the attacker's authorization code and log the victim into the attacker's account.

Wallos before version 4.9.4 has an authentication bypass vulnerability in the endpoints/db/migrate.php endpoint. This endpoint executes database schema migrations when called over HTTP with zero authentication. Any unauthenticated attacker can trigger pending migration files against the live SQLite database.

Incorrect access control in the showSyslog function of TOTOLINK T6 allows unauthenticated attackers to retrieve recent system logs by sending a crafted POST request to /cgi-bin/cstecgi.cgi.

A flaw was found in GDB's STABS debug format parser. The read_member_functions() function in gdb/stabsread.c contains a linked list removal bug in the code that separates destructor and non-destructor member functions of C++ classes. The bug causes the destructor entries to remain in the main function list while the list length counter is decremented, resulting in an out-of-bounds write when the function list is copied to its final allocated array. An attacker can craft an ELF binary with malicious .stab and .stabstr sections that triggers this out-of-bounds write when a user opens the file in GDB and performs any symbol-inspection operation such as setting a breakpoint. The inferior process does not need to be executed. Under controlled conditions, this was demonstrated to achieve execution of arbitrary commands within the GDB process.

Unrestricted deserialization of untrusted data in the cursor pagination component in the OpenSearch SQL plugin allows a remote authenticated user with basic read/search permissions to execute arbitrary code on the server by sending a crafted cursor parameter to the plugins/sql endpoint.

Pangolin before 1.22.0 contains an authentication bypass vulnerability that allows unauthenticated attackers to access any protected resource by supplying an attacker-controlled URL parameter to the share-link authentication endpoint that omits the expected resource identifier from the token verification call. Attackers holding a single valid share link for any resource can authenticate against arbitrary resources across different organizations, bypassing all configured authentication methods including SSO, resource passwords, PIN codes, email allowlists, and header authentication.

Goploy is an open-source automation deployment system. Prior to version 1.18.0, a severe path traversal vulnerability exists in its backend API endpoints, specifically /deploy/fileDiff (File Compare), when handling file paths provided by the client.

oasdiff-action is a GitHub Action that detects breaking changes in OpenAPI specs and post a review on every pull request. Before version 0.0.51, the oasdiff actions resolved external $refs in the OpenAPI spec by default (allow-external-refs: true). When an action runs on a pull request whose spec is attacker-controlled – most importantly fork pull requests on public repositories – a $ref in that spec is fetched/read on the runner with no interaction required, enabling SSRF and disclosure of structured files on the runner.

A flaw has been found in MegaEase EaseProbe up to 2.3.0. The function realIP in web/server.go of the Middleware component is affected. Manipulation of X-Forwarded-For/X-Real-IP/True-Client-IP arguments causes improper access controls. The attack can be initiated remotely, and the exploit has been published.

MCPHub prior to version 1.0.30 does not enforce ownership restrictions in the tool-execution API. Any authenticated non-admin user can invoke tools on MCP servers owned by other users, even if they cannot see those servers in GET /api/servers. This can lead to arbitrary host file read (e.g., /etc/passwd) and SSRF.

MCPHub prior to version 1.0.32 has an SSRF guard flaw in src/utils/ssrf.ts. The isBlockedIpv6 function only checks for loopback, link-local, unique-local, IPv4-mapped, and IPv4-compatible IPv6 addresses, but not IPv6 transition address families (NAT64, 6to4, Teredo). An attacker can encode a private IPv4 address in these IPv6 forms to bypass the guard and reach internal infrastructure.

MCPHub prior to version 1.0.32 allows an authenticated non-admin user to register a server pointing at an arbitrary URL and make the hub issue server-side requests to it, with no egress filtering (no block of loopback / RFC1918 / link-local). Via the OpenAPI proxy path the response body is returned to the caller (full, reflected SSRF); via the SSE/streamable-http transport the request is sent blind.

MCPHub prior to version 1.0.31 has an authorization flaw for bearer keys with accessType 'servers' or 'custom' used against group routes. isBearerKeyAllowedForRequest grants access to the entire group as long as any single server in that group appears in the key's allowedServers list, without re-checking after authorization. A key scoped to one server also grants full access to every other server in the group.

MCPHub prior to version 1.0.32 does not perform role checking in the built-in prompt and resource controllers. The mutating POST/PUT /api/prompts* and POST/PUT /api/resources* routes are attached to the authenticated router with no admin gate, and the handlers never read req.user. A non-admin can create, overwrite, and shadow global prompt templates and resources that all other users are served.

MCPHub prior to version 1.0.29 has a flaw in the PUT /api/system-config endpoint (handler updateSystemConfig) that performs no authorization check. It is protected only by the app-wide authentication middleware and a rate limiter, but never inspects req.user.isAdmin.