Get Custom Field Values Project maintains a specialized utility focused on custom field manipulation, with its vulnerability profile centered on web-layer input handling. The observed weaknesses recur around cross-site scripting and authorization issues characteristic of web-facing data-access tools. Live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Get Custom Field Values Project over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2021-24872MEDIUM The Get Custom Field Values WordPress plugin before 4.0 allows users with a role as low as Contributor to access other posts metadata without validating the permissions. Eg. contri | Dec 13, 2021 | 6.5 | 22 | NO | NO |
CVE-2021-24871MEDIUM The Get Custom Field Values WordPress plugin before 4.0.1 does not escape custom fields before outputting them in the page, which could allow users with a role as low as contributo | Dec 13, 2021 | 5.4 | 20 | NO | NO |
CVE-2023-45604MEDIUM Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Scott Reilly Get Custom Field Values plugin <= 4.0.1 versions. | Oct 18, 2023 | 4.8 | 15 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Get Custom Field Values Project.
Media articles that mention a CVE ID that affects a product developed by Get Custom Field Values Project — matched by CVE ID, not by vendor name.