← WordPress Vulnerabilities
WordPress security by component

DesignThemes Core Features

DesignThemes Core Features is a WordPress component with 3 published CVE records in this archive. The latest tracked vulnerability was published Feb 20, 2026; the highest published CVSS base score is 7.5.

Plugin slug: designthemes-core-features

CVE-2025-69302: DesignThemes Core Features: Cross-site scripting

DesignThemes Core Features is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.

PublishedFeb 20, 2026
Safe version guidanceSee mitigation notes
Published vulnerabilities for designthemes-core-features
Safe version
Feb 20, 2026 CVE-2025-69302
DesignThemes Core Features: Cross-site scripting
DesignThemes Core Features is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
See mitigation notes
CVE7.1
NVDPending
Mar 25, 2025 CVE-2025-0845
DesignThemes Core Features: Cross-site scripting
DesignThemes Core Features is affected by cross-site scripting. Exploitation requires an authenticated contributor account. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
See mitigation notes
CVE6.4
NVDPending
Mar 05, 2025 CVE-2024-13471
DesignThemes Core Features: A security weakness
DesignThemes Core Features is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
See mitigation notes
CVE7.5
NVDPending