Is Smart Custom Fields safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (5.0.8). As of 2026-11-04. 4 issues are on record for older versions; version 5.0.8 or newer fixes all of them that state a fix. Keep Smart Custom Fields on the latest version (5.0.8) and remove it if you do not use it.

Which versions of Smart Custom Fields are vulnerable?

Known issues on record (newest first): Stored cross-site scripting (XSS) (5.0.7 and older, fixed in 5.0.8); Missing authorization check (5.0.6 and older, fixed in 5.0.7); Stored cross-site scripting (XSS) (5.0.0 and older, fixed in 5.0.1); Missing authorization check (4.2.2 and older, fixed in 5.0.0). The full list with sources is on this page.

What is the latest version of Smart Custom Fields?

5.0.8, according to wordpress.org (last updated 2026-07-16). It has 50,000+ active installs.

What should I do if my Smart Custom Fields is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update smart-custom-fields). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · smart-custom-fields · data as of 2026-11-04

Is Smart Custom Fields safe? Known vulnerabilities and latest version

Latest version: 5.0.8
Last updated: 2026-07-16
Active installs: 50,000+
Known issues on record: 4
Unpatched in latest: 0
Tested up to WP: 6.8.12 · PHP 7.4+

Smart Custom Fields is a simple plugin for managing custom fields. — by Takashi Kitajima

What to do

Update to the latest version (5.0.8). Anything older than 5.0.8 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get smart-custom-fields --field=version shows what you run; wp plugin update smart-custom-fields updates it.

Check your version

Known vulnerabilities

4 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 6.4 CVE-2026-2594 · published 2026-07-17

Stored cross-site scripting (XSS) in Smart Custom Fields (5.0.7 and older)

Affected: 5.0.7 and older
Fixed in: 5.0.8 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Smart Custom Fields plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 5.0.7. This is due to insufficient input sanitization and output escaping of uploaded image attachment titles. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. NOTE: This vulnerability was partially patched in 5.0.7.

NVD CVE-2026-2594 Wordfence advisory Code change (fix)

medium 4.3 CVE-2026-4066 · published 2026-03-23

Missing authorization check in Smart Custom Fields (5.0.6 and older)

Affected: 5.0.6 and older
Fixed in: 5.0.7 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Smart Custom Fields plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the relational_posts_search() function in all versions up to, and including, 5.0.6. This makes it possible for authenticated attackers, with Contributor-level access and above, to read private and draft post content from other authors via the smart-cf-relational-posts-search AJAX action. The function queries posts with post_status=any and returns full WP_Post objects including post_content, but only checks the generic edit_posts capability instead of verifying whether the requesting user has permission to read each individual post.

NVD CVE-2026-4066 Wordfence advisory Code change (fix)Plugin source

medium 6.5 CVE-2025-22308 · published 2025-01-07

Stored cross-site scripting (XSS) in Smart Custom Fields (5.0.0 and older)

Affected: 5.0.0 and older
Fixed in: 5.0.1
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Takashi Kitajima Smart Custom Fields smart-custom-fields allows Stored XSS.This issue affects Smart Custom Fields: from n/a through <= 5.0.0.

NVD CVE-2025-22308 Patchstack advisory

medium 4.3 CVE-2024-1995 · published 2024-03-20

Missing authorization check in Smart Custom Fields (4.2.2 and older)

Affected: 4.2.2 and older
Fixed in: 5.0.0 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

NVD CVE-2024-1995 Wordfence advisory Code change (fix)github.com Plugin source

Recent activity

2026-07-16 — latest release on wordpress.org (5.0.8).
2026-07-17 — Stored cross-site scripting (XSS) disclosed (CVE-2026-2594), fixed in 5.0.8.
2026-03-23 — Missing authorization check disclosed (CVE-2026-4066), fixed in 5.0.7.
2025-01-07 — Stored cross-site scripting (XSS) disclosed (CVE-2025-22308), fixed in 5.0.1.

Free. We check the CVE feeds every day and email you only when a new issue for Smart Custom Fields (smart-custom-fields) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site scripting (XSS) (2) · Missing authorization (2)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/smart-custom-fields (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/smart-custom-fields"><img src="https://laskyr.com/plugins/smart-custom-fields/badge.svg" alt="Smart Custom Fields vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is Smart Custom Fields safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (5.0.8)

What to do

Check your version

Known vulnerabilities

Stored cross-site scripting (XSS) in Smart Custom Fields (5.0.7 and older)

Missing authorization check in Smart Custom Fields (5.0.6 and older)

Stored cross-site scripting (XSS) in Smart Custom Fields (5.0.0 and older)

Missing authorization check in Smart Custom Fields (4.2.2 and older)

Recent activity

Get an email when Smart Custom Fields has a new vulnerability

Browse vulnerabilities

Where this data comes from