CVE-2025-31395
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in a.ankit Easy Custom CSS easy-custom-css allows Stored XSS.This issue affects Easy Custom CSS: from n/a through <= 1.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Easy Custom CSS WordPress plugin by developer a.ankit versions 1.0 and below contains a CSRF vulnerability that allows attackers to inject malicious scripts (Stored XSS) through crafted form submissions. The lack of proper CSRF token validation on CSS customization forms enables attackers to trick authenticated administrators into submitting malicious requests that persist malicious JavaScript code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Easy Custom CSS plugin is installedCheck for the plugin directory at /wp-content/plugins/easy-custom-css/ or list installed WordPress plugins and search for 'Easy Custom CSS' by developer a.ankitAffected if Plugin directory exists or plugin appears in WordPress admin plugin list
-
Confirm installed plugin versionOpen the main plugin file (easy-custom-css.php) and look for the version comment in the plugin header (e.g., 'Version: 1.0' or lower)Affected if Version is 1.0 or below, or version field is missing/empty indicating unversioned release
-
Identify CSS customization form endpointSearch plugin files for form tags with action attributes, particularly looking for forms that handle CSS input (search for 'custom_css', 'css', or '<form' in PHP files)Affected if Plugin contains forms that accept and store CSS content from users
-
Check for CSRF protection in form handlingExamine the PHP file that processes the CSS form submission. Search for 'wp_nonce_field', 'wp_verify_nonce', 'nonce', or 'check_admin_referer' functions around the form processing codeAffected if No nonce verification or CSRF token validation is found in the form processing logic, or forms submit without any token verification step
-
Check if CSS storage and display allow script injectionLook for how stored CSS is retrieved and output. Verify if there is any sanitization (esc_attr, esc_html, wp_strip_all_tags) or encoding applied before displaying saved CSS back to usersAffected if Stored CSS content is displayed without proper escaping or sanitization, allowing injected JavaScript to execute in admin browsers
User is affected if the Easy Custom CSS plugin (version 1.0 or below) is installed and active, with its CSS customization form lacking CSRF token validation and proper output encoding.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement nonces and CSRF tokens for all form submissions in the plugin, add proper input sanitization for CSS customizations, and apply output encoding when displaying stored CSS content to prevent XSS execution.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31395 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-31395 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data