CVE-2025-46435
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 Yash Binani Time Based Greeting time-based-greeting allows Stored XSS.This issue affects Time Based Greeting: from n/a through <= 2.2.2.
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 confidenceA CSRF vulnerability in the Time Based Greeting WordPress plugin (versions <= 2.2.2) allows authenticated administrators to be tricked into storing malicious JavaScript payloads via form submissions. Attackers can craft malicious links or pages that, when visited by a logged-in admin, submit crafted requests to inject stored XSS into plugin settings.
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 Time Based Greeting plugin is installedCheck for the plugin directory at /wp-content/plugins/time-based-greeting/ or search for 'Time Based Greeting' in the WordPress plugins admin panelAffected if Plugin directory or entry exists in WordPress plugins
-
Identify installed plugin versionOpen the main plugin file (typically time-based-greeting.php) and locate the Version header in the plugin comment block at the top, or check in WordPress admin under Plugins > Installed PluginsAffected if Version number is 2.2.2 or lower
-
Verify form submissions lack CSRF protectionExamine the main plugin PHP file for form handling code - search for '$_POST' or '$_REQUEST' submissions and check if they include WordPress nonce verification using 'wp_verify_nonce' or 'check_admin_referer' before processingAffected if Form handling code processes POST requests without nonce validation
-
Inspect admin settings pages for stored XSS entry pointsReview the plugin settings code for any fields that accept user input and store it to the database without sanitization (such as using update_option without sanitize_text_field or similar escaping functions)Affected if Plugin settings are saved with insufficient input sanitization enabling stored XSS
A user is affected if the Time Based Greeting plugin is installed at version 2.2.2 or below AND the plugin processes form submissions without WordPress nonce verification, allowing CSRF attacks to inject malicious JavaScript into plugin settings.
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 dataUpdate the plugin to a patched version once available, or implement anti-CSRF tokens using WordPress nonces on all form submissions and AJAX actions within the plugin, combined with proper output sanitization.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46435 — 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-46435 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