Security readout for executives and security teams
Plain-English summary
CVE-2025-46435 affects the WordPress Time Based Greeting plugin up to version 2.2.2. A malicious site could trick a logged-in WordPress user into making a change that stores harmful script in the site, creating browser-side risk for later visitors or administrators.
Executive priority
Prioritize remediation for public WordPress sites using this plugin, especially business-critical sites. The issue is high severity but not shown as actively exploited in the provided sources, so urgency should be driven by plugin presence and administrative exposure.
Technical view
The source describes a CWE-352 CSRF issue that can lead to stored XSS in Time Based Greeting <=2.2.2. CVSS 3.1 is 7.1: network reachable, low complexity, no attacker privileges, user interaction required, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely limited to WordPress installations that have the Time Based Greeting plugin installed at version 2.2.2 or earlier. The affected-version metadata in the bundle is sparse, so confirm against the installed plugin slug and vendor records.
Exploitation context
The bundle says CISA KEV is false and provides no cited evidence of active exploitation. Practical abuse requires user interaction, likely by tricking a logged-in WordPress user into a forged request that stores script through vulnerable plugin functionality.
Researcher notes
Do not assume broader WordPress or theme impact from this record. The evidence identifies CSRF leading to stored XSS in a specific plugin version range, but does not provide exploit details, a patched version, or active exploitation confirmation.
Mitigation direction
- Inventory WordPress sites for the time-based-greeting plugin.
- Treat installed versions <=2.2.2 as affected pending vendor confirmation.
- Check Patchstack and vendor guidance for a fixed release or official mitigation.
- Disable or remove the plugin if no trusted fix is available.
- Restrict WordPress administrative access to trusted users and sessions.
Validation and detection
- Confirm plugin presence, slug, and installed version across WordPress assets.
- Review plugin configuration and stored greeting content for unexpected script or markup.
- Check WordPress logs for unusual administrator actions around plugin settings.
- Verify whether Patchstack or vendor records identify a patched version.
- Record compensating controls if the plugin cannot be removed promptly.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-46435 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/time-based-greeting/vulnerability/wordpress-time-based-greeting-plugin-2-2-2-csrf-to-stored-xss-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.