VulnTitan VulnTitan Security command center
Plugin Vulnerability Hub
Plugin 1 known issue Latest disclosed Dec 31, 2025

Custom Style Vulnerabilities

Review known vulnerability records for the WordPress plugin Custom Style (`custom-style`), including severity, CVE references, affected versions, and patch status.

Recent tracked CVEs on this page include CVE-2025-49342, so operators can jump from disclosure to patch validation without scanning the full feed first.

View on WordPress.org Back to Feed
Known Records
1
High or Critical
0
Patch Coverage
100%
Last Updated
Jan 05, 2026
Related Security Guides

Use these guides while reviewing Custom Style fixes

Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.

Hardening
WordPress hardening checklist for exposed plugins

Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Plugin Security
WordPress plugin security basics for patch decisions

Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Scanning
WordPress vulnerability scanner buyer's guide

Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Patch Decision Workflow

How to prioritize Custom Style remediation

Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.

Search-Ready Records
1
1. Match the Package
Confirm the installed WordPress plugin slug is custom-style before acting on any CVE from this cluster.
2. Sort by Severity
Start with 0 high or critical records, then review medium and unrated findings with public references.
3. Check Patch Evidence
1 record include a patch path; verify compatibility before closing the finding.
4. Monitor Gaps
0 records still lack a listed fixed release, so keep this hub in the review queue.
High-Signal Remediation Targets
CVE-2025-49342 Medium
Cross-Site Request Forgery remediation for Custom Style

Affected range: Versions up to 1.0. Fixed version is not listed yet.

Priority CVE Quick Links

Fast paths into Custom Style CVE reports

Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.

Indexed CVEs
1
Tracked CVE Issue Type Affected Versions Fixed Version CVSS
CVE-2025-49342
Custom Style <= 1.0 - Cross-Site Request Forgery
 Cross-Site Request Forgery Versions up to 1.0 No patch listed CVSS 4.3
CVE-2025-49342 Medium No patch listed
CVE-2025-49342 Custom Style Cross-Site Request Forgery

Custom Style <= 1.0 - Cross-Site Request Forgery

Coverage Snapshot

What this page helps you verify fast

This hub clusters tracked records for Custom Style so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.

Patch Visibility
1 record include a published patch path, leaving 0 with no listed safe release yet.
Severity Mix
0 critical and 0 high severity findings.
Recent CVEs
CVE-2025-49342
Reference Workflow
Jump from the hub into the full report when you need remediation notes, exploit context, CVSS vectors, or source references.
Triage First

Open the records most likely to drive action

These recent records surface the CVE strings, patch cues, and direct report links most operators need first.

Known Vulnerabilities

Reports for Custom Style

Sorted by latest disclosure date so newly published issues surface first.

Plugin Medium Patched: No CVE-2025-49342
CVE-2025-49342: Custom Style <= 1.0 - Cross-Site Request Forgery

The Custom Style plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.0. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action via...

Published
Dec 31, 2025
Patched Release
Not published
Affected Versions
Versions up to 1.0
Next Step
Open the full report for remediation notes and references.
Review CVE-2025-49342 fixed version details Open CVE Reference