CVE-2025-48351
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 PluginsPoint Kento Splash Screen kento-splash-screen allows Stored XSS.This issue affects Kento Splash Screen: from n/a through <= 1.4.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Kento Splash Screen WordPress plugin (versions <=1.4) allows authenticated administrators to be tricked into submitting malicious requests that inject and store XSS payloads into the plugin's settings or splash screen content.
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.
-
Confirm plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and look for 'Kento Splash Screen'. Note the version number displayed. Alternatively, check the plugin files in /wp-content/plugins/ for a version marker.Affected if Plugin is installed and version is 1.4 or lower
-
Inspect admin form handlers for nonce verificationExamine the plugin's main PHP file(s) for form handling code (typically in admin menu callback functions). Look for the presence of wp_verify_nonce or check_admin_referer before processing form submissions.Affected if No nonce verification is found in form processing code, indicating the CSRF vulnerability is present
-
Check plugin settings for stored XSS contentNavigate to the plugin's settings page (usually under Settings or a dedicated menu item). Inspect form fields for any suspicious script tags, javascript: URLs, or event handler attributes in the splash screen content fields.Affected if Any unexpected HTML, script tags, or event handlers are found stored in the plugin settings
-
Review HTTP requests for missing CSRF tokensUse browser developer tools to capture a plugin settings form submission. Inspect the request payload for a '_wpnonce' or '_wpnonce' parameter and verify it changes on each page load.Affected if The form submission does not include a nonce token parameter
A user is affected if the Kento Splash Screen plugin version is 1.4 or lower and the admin settings forms lack nonce verification, allowing stored XSS to be injected via CSRF.
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 WordPress nonce verification (wp_verify_nonce) on all form submissions and admin actions to prevent CSRF attacks; update to patched version when available.
- 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-48351 — 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-48351 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