Smart Custom Fields
Approved changes feed: RSS · Atom
cpe:2.3:a:inc2734:smart_custom_fields:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Inc2734 (f54a108b-b9d4-5dc6-b196-a28f927026d2) |
|---|---|
| Product | Smart Custom Fields (68c17c10-017c-5be7-b91f-478a874976e5) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-2594 |
vulnerable | 2026-07-29 00:37:44.999528 |
Smart Custom Fields <= 5.0.7 - Authenticated (Author+) Stored Cross-Site Scripting via Attachment Title
MEDIUM (6.4)
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.
Published: 2026-07-17T01:30:50.365Z
Updated: 2026-07-17T15:07:53.149Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-4066 |
vulnerable | 2026-06-08 08:05:12.561133 |
Smart Custom Fields <= 5.0.6 - Missing Authorization to Authenticated (Contributor+) Sensitive Information Exposure via Relational Post Search
MEDIUM (4.3)
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.
Published: 2026-03-23T22:25:39.149Z
Updated: 2026-04-08T17:05:11.962Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-22308 |
vulnerable | 2026-06-08 07:10:52.818626 |
WordPress Smart Custom FIelds plugin <= 5.0.0 - Cross Site Scripting (XSS) vulnerability
MEDIUM (6.5)
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.
Published: 2025-01-07T10:48:57.311Z
Updated: 2026-04-28T16:10:58.981Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1995 |
vulnerable | 2026-06-08 06:27:15.213358 |
Smart Custom Fields <= 4.2.2 - Missing Authorization to Authenticated (Subscriber+) Post Content Disclosure
MEDIUM (4.3)
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, 4.2.2. This makes it possible for authenticated attackers, with subscrber-level access and above, to retrieve post content that is password protected and/or private.
Published: 2024-03-20T01:58:04.811Z
Updated: 2026-04-08T17:30:45.686Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.