Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.

Threats Tagged 'cwe-940'

View all threats tagged with 'cwe-940'. Filter and sort to focus on specific types of threats.

Pro Console Lifetime

Stop chasing alerts. Route them.

Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.

Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Tag: cwe-940

Threats Tagged 'cwe-940'

Click on any threat for detailed analysis and mitigation recommendations

CVE-2026-78685: CWE-940 Improper Verification of Source of a Communication Channel in Le-yan Medical Practice Management SystemCVE-2026-78685
0

Le-yan Medical Practice Management System version 2.4.2.8 contains a remote code execution vulnerability due to improper verification of the source of a communication channel. This flaw allows unauthenticated remote attackers to execute arbitrary operating system commands by delivering a crafted HTML page. The vulnerability is identified as CWE-940 and has a high severity with a CVSS score of 8.8.

Join the discussion
CVE-2026-73419: CWE-345: Insufficient Verification of Data Authenticity in nextauthjs next-authCVE-2026-73419
0

NextAuth.js provides authentication for Next.js. Prior to@auth/core 0.41.3 and next-auth 4.24.15 and 5.0.0-beta.32, Auth.js stores the OAuth/OIDC anti-CSRF checks state, nonce, and the PKCE verifier in global cookies that are not bound to the provider that created them. On callback, a check value minted during a sign-in started with one provider can satisfy the callback for a different provider because the stored cookie is not verified against the callback provider's identity, including the provider ID, issuer, client ID, or redirect URI. In a multi-provider application that permits account linking while logged in, when one provider's authorization request is observable and a target provider callback can be satisfied without a PKCE verifier, an attacker can lure a victim into starting a legitimate same-origin flow and link the attacker's target-provider account to the victim's Auth.js user. The linked provider grants the attacker persistent sign-in to the victim's account, while cross-site request forgery alone is insufficient. This issue is fixed in @auth/core 0.41.3 and next-auth 4.24.15 and 5.0.0-beta.32.

Join the discussion

Showing 1 to 2 of 2 results

Filters:Tag: cwe-940
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses