Skip to main content
VulnerabilityPublished

CVE-2026-125783: Custom Post Types and Custom Fields creator (WordPress plugin) · Cross-site Scripting

Affects Custom Post Types and Custom Fields creator (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 2.4.2 soon.

Data as of 13 Nov 2026, 15:33 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Patchstack)CVSS 3.17.1
Patch
Available – fixed in 2.4.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade Custom Post Types and Custom Fields creator (WordPress plugin) to 2.4.2.

Affected software

ProductAffectedFixed in
Custom Post Types and Custom Fields creator – WCKwck-custom-fields-and-custom-post-types-creatorAffected
  • <2.4.2
Fixed in
  • 2.4.2

AI-suggested

Upgrade the Custom Post Types and Custom Fields creator – WCK plugin to version 2.4.2 or later, where this vulnerability is fixed. No other mitigation actions are specifically indicated.

Description

CVE-2026-125783 is a high-severity reflected cross-site scripting (XSS) vulnerability in the WordPress plugin Custom Post Types and Custom Fields creator – WCK by madalin.ungureanu. It affects versions from initial releases up to 2.4.0 and allows improper neutralization of input during web page generation, potentially leading to script injection. The issue is fixed in version 2.4.2.

References

Community reviews

Loading reviews…