CVE-2022-1966
Unknown
Last modified
This CVE is reserved or rejected; no details have been published by NVD.
Description
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2022-32250. Reason: This candidate is a duplicate of CVE-2022-32250. Notes: All CVE users should reference CVE-2022-32250 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.
Timeline
- Published
- Last Modified
- Status
- Rejected
Related CVEs from 2022
- CVE-2022-1960The MyCSS WordPress plugin through 1.1 does not have CSRF ch…4.3
- CVE-2022-1961The Google Tag Manager for WordPress (GTM4WP) plugin is vuln…4.8
- CVE-2022-1962Uncontrolled recursion in the Parse functions in go/parser b…5.5
- CVE-2022-1963An issue has been discovered in GitLab CE/EE affecting all v…5.3
- CVE-2022-1964The Easy SVG Support WordPress plugin before 3.3.0 does not …5.4
- CVE-2022-1965Multiple products of CODESYS implement a improper error hand…8.1
- CVE-2022-1967The WP Championship WordPress plugin before 9.3 is lacking C…6.5
- CVE-2022-1968Use After Free in GitHub repository vim/vim prior to 8.2.7.8
- CVE-2022-1969The Mobile browser color select plugin for WordPress is vuln…8.8
- CVE-2022-1970Rejected reason: The originally reported issue in https://gi…
- CVE-2022-1971The NextCellent Gallery WordPress plugin through 1.9.35 does…4.8
- CVE-2022-1972Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
Are you affected by CVE-2022-1966?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
