SQL injection in WP Go Maps WordPress plugin (all versions before 10.1.04) allows unauthenticated network attackers to read data from the underlying WordPress database by injecting malicious SQL syntax into an unsanitized plugin parameter. Reported by WPScan, a publicly available proof-of-concept exploit exists for this flaw; however, CISA KEV does not list active exploitation, and EPSS at 0.18% (7th percentile) indicates low observed exploitation probability in the wild. The SSVC framework's 'non-automatable' classification and the CVSS AC:H rating indicate that exploitation requires attacker effort beyond trivial scripting, moderating the real-world urgency despite the unauthenticated attack vector.
Unauthenticated download of exported member and payment PII is possible in the Paid Membership Subscriptions WordPress plugin before 3.0.7 due to export files being written to a predictable, unprotected path within the publicly accessible uploads directory. Any site running an affected version where an administrator has recently triggered an export is at risk of exposing member personally identifiable information and payment records to any network-accessible attacker. A publicly available proof-of-concept exploit exists per WPScan, and while the CVSS base score is low (3.7), the data sensitivity of the exposed artifact elevates real-world impact beyond what the score alone suggests.
Missing authorization on attachment download endpoints in the Support Genix WordPress plugin (before 1.4.48) exposes private support ticket files to unauthenticated network access. Any caller who possesses a stored attachment's filename can retrieve it directly, bypassing ticket ownership and login checks entirely. A publicly available exploit exists per WPScan, though EPSS sits at 0.14% (4th percentile), indicating no widespread opportunistic exploitation at time of analysis; no CISA KEV listing.
Unauthenticated order document enumeration in the FluentCart WordPress plugin (all versions before 1.5.3) exposes customer PII - names, email addresses, and billing and shipping postal addresses - across every order in a store. CWE-639 (IDOR) is the root cause: order documents are keyed on sequential numeric identifiers with no authorization or ownership validation, so any unauthenticated visitor can iterate through all historical orders. A publicly available exploit exists per WPScan; no active exploitation is confirmed in CISA KEV, though the trivial enumeration method and public PoC substantially lower the barrier to mass data harvesting.
Stored XSS in ElementsKit Elementor Addons (WordPress plugin before 3.10.01) allows administrative users to inject malicious JavaScript into megamenu menu-item settings, which is rendered unsanitized to all page visitors. The most critical exploitation path targets WordPress multisite networks: a subsite Administrator - a role WordPress normally bars from injecting raw HTML via the unfiltered_html capability - can bypass this restriction through the plugin's misconfigured save routine, planting a payload that executes in Super Admin and site visitor sessions. A publicly available proof-of-concept exists per WPScan; EPSS is low (0.16%) but SSVC flags total technical impact due to the Super Admin session takeover potential on multisite deployments.
Wildcard domain validation in Keycloak's keycloak-services component can be bypassed by an attacker who controls their connection's reverse DNS, enabling unauthorized client registration or modification against a Keycloak realm. The flaw stems from the system accepting any hostname that merely ends with the configured domain suffix (e.g., 'attackerexample.com' satisfying a '*.example.com' restriction) rather than enforcing true subdomain membership. Exploitation requires high attack complexity due to the reverse DNS control prerequisite, and no public exploit or CISA KEV listing has been identified at the time of analysis.
HCL iControl versions 4.3.0 and 4.4.0 expose internal configuration files to local access due to improper web server or application hardening, classified under CWE-497 (Exposure of Sensitive System Information). Local actors without any privileges can read configuration data that should be restricted, potentially revealing sensitive system details usable for follow-on attacks. No public exploit or active exploitation has been identified at time of analysis, and the CVSS score of 4.0 (Medium) reflects the limited local attack surface.
HCL iControl versions 4.3.0 and 4.4.0 publicly expose internal configuration files due to inadequate web server or application hardening, mapping to CWE-15 (External Control of System or Configuration Setting). The misconfiguration allows attackers to retrieve sensitive configuration data that may contain credentials, internal paths, service endpoints, or other operational details usable for further lateral movement or privilege escalation. No active exploitation has been confirmed in CISA KEV, and no public exploit code has been identified at the time of analysis.
Cross-job file read in Contao CMS 5.7.0-5.7.6 allows authenticated backend users to exfiltrate job attachments belonging to other jobs by injecting path traversal sequences into the attachment identifier parameter. The job attachment download controller authorizes only the jobUuid route parameter, then constructs the actual file path by joining that authorized UUID with the attacker-supplied identifier; Contao's VirtualFilesystem::resolve() canonicalizes the combined path but rejects only escapes from the filesystem mount, not cross-job traversals within the mount. No public exploit has been identified at time of analysis, and the CVSS 3.1 Low score of 3.1 reflects meaningful exploitation barriers: backend authentication and prior knowledge of a victim job UUID are both required.
Server-Side Request Forgery in Contao CMS's Feed Reader front-end module enables authenticated backend users to pivot the web server against internal network resources, cloud metadata endpoints, or loopback services. Affected are Contao 5.3.35-5.3.47 and 5.7.0-RC1-5.7.8; exploitation requires a backend account with module-edit permissions. No public exploit code has been identified and the vulnerability is not listed in CISA KEV; risk is primarily relevant to multi-tenant or SaaS Contao deployments where untrusted backend users exist.
sigstore-go versions up to and including 1.2.0 accept Sigstore bundles signed with expired long-lived public keys because the verifier omits the timestamp-validity check when using `ExpiringKey`-wrapped verifiers. An attacker who obtains expired signing key material can produce bundles that pass verification despite the key's configured expiry window, undermining supply chain integrity guarantees enforced by key rotation policies. This affects only the self-managed long-lived key workflow - standard Sigstore deployments using Fulcio certificate authorities are explicitly unaffected. No public exploit identified at time of analysis.
Contao CMS's crawler leaks HTTP authentication credentials to external hosts due to an option-name mismatch in its credential-scrubbing logic, affecting versions 4.13.40-5.3.46 and 5.7.0-RC1-5.7.6. The cleaner is coded to remove the non-existent keys `basic_auth` and `bearer_auth` rather than Symfony HttpClient's actual `auth_basic` and `auth_bearer` options, so credentials configured in `contao.crawl.default_http_client_options` are silently passed through to external domains. An attacker who can place an external link on any page crawled by Contao's broken-link checker can receive those credentials on an attacker-controlled server. No public exploit or CISA KEV listing exists at time of analysis.
Open redirect in Serendipity's exit.php allows unauthenticated attackers to craft URLs on a legitimate blog domain that silently forward victims to arbitrary attacker-controlled sites. All Serendipity installations prior to version 2.6.1 are affected, but only when the Track Exits plugin is active and configured with commentredirection set to "s9y" - a non-default, explicit setting. No public exploit code and no CISA KEV listing exist at time of analysis; the CVSS 4.0 score of 2.1 reflects limited direct technical impact, though the phishing, malware-delivery, and URL-reputation-bypass potential represents meaningful real-world risk for organizations where blog domain credibility matters.
CRLF injection in ufirstgroup's ymlr Elixir YAML library (versions 0.0.1 through < 5.1.6) allows an attacker who controls comment strings passed to any Ymlr document function to inject arbitrary content into the generated YAML output by embedding newline characters. Because ymlr emits each comment as '# {string}\n' without inspecting the string for embedded line breaks, anything after the first newline exits comment context and is written as raw YAML body content, enabling forged mapping keys, value overrides, and document-boundary markers. Every document-encoding entry point - document!/2, document/2, documents!/2, and documents/2 - shares the same vulnerable code path. No confirmed active exploitation or public exploit code exists at time of analysis; the CVSS 4.0 score of 2.1 reflects the constrained preconditions required.