recorded together · two weakness classes
Cross-Site Request Forgery and Misconfiguration and Insecure Design
10 CVEs
10 CVEs name a weakness of both Cross-Site Request Forgery and Misconfiguration and Insecure Design, too few to compare with chance. The pairing most often behind it is CWE-1275 (Sensitive Cookie with Improper SameSite Attribute) with CWE-614 (Sensitive Cookie in HTTPS Session Without 'Secure' Attribute), in 3 CVEs.
Every dot is a CVE whose record names a weakness from both classes, neither being the other's parent in the CWE hierarchy. The named ones come first: exploited in the wild, then those with a public check, then the likeliest to be.
- CVEs that carry a weakness of both
- 10
- Chance alone would give
- about 28
- So they are recorded together
- too few CVEs to say
A CVE counts when its record names a weakness from each class, neither being the other's parent. It says the two kinds of flaw are recorded together in one vulnerability more or less often than chance: not that one causes the other, and it follows how the people who file CVEs choose CWEs.
How this is weighed, and the sources
Chance is what the two classes' shares of all CVEs that carry weaknesses of two or more classes would give if weaknesses paired at random. A line is drawn on the dial from 25 CVEs and 1.15 times chance. Weaknesses are the CWEs the CVE List and NVD record; exploitation is CISA KEV, likelihood is EPSS.
Every one of the 10 is a mark on the map. Named now: 1 to 10, most at risk first.
- IBM InfoSphere Information Server 9.1, 11.3, 11.5, and 11.7 is vulnerable to cross-frame scripting which is a vulnerability that allows an attacker to load Information Server comp…
- Parts of the Puppet Enterprise Console 3.x were found to be susceptible to clickjacking and CSRF (Cross-Site Request Forgery) attacks. This would allow an attacker to redirect use…
- OpenAM Insecure SSO Cookie Initialization
- Joro: Unauthenticated Cross-Origin Plugin Upload Leads to RCE
- Mockoon: Unauthenticated admin API + wildcard CORS allows mock-state hijack and secret theft
- Improper Access Control In DestinyECM
- MISP automation endpoints may be exposed to CSRF when Sec-Fetch-Site protection is disabled by default
- Misskey CSRF vulnerability due to insecure configuration of authentication cookie attributes
- Use of unsecure cookies for GraphicalData web service and WebClient web app
- WebDyne versions from 2.014 before 3.022 for Perl issue session cookies without the Secure, HttpOnly and SameSite attributes
exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.