WordPress plugin · get-custom-field-values
Is Get Custom Field Values safe?
Not updated in years.
Last updated Oct 10, 2023. Nothing on record is unpatched, but a plugin nobody maintains won’t get a fix when the next flaw is found. Treat it as abandoned.
- Flaws on record
- 3
- High or critical
- 0
- Exploited
- none
- Current version
- 4.1
- Last updated
- Oct 10, 2023
- Active installs
- 1,000+
Every recorded flaw
- Oct 18, 2023Auth.CVE-2023-45604 · fixed in 4.1 · reported by PatchstackMedium 5.9
- Dec 13, 2021Get Custom Field Values: Allows users with a roleCVE-2021-24872 · fixed in 4.0 · reported by WPScan1.0% oddsMedium 6.5
- Dec 13, 2021Get Custom Field Values: Does not escape custom fields before outputting them in the pageCVE-2021-24871 · fixed in 4.0.1 · reported by WPScanMedium 5.4
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.