Security readout for executives and security teams
Plain-English summary
A WordPress site using Noo Timetable up to 2.1.3 may let an attacker trick a logged-in user into making unintended plugin-related changes. The cited impact is limited to integrity, not data theft or outage. It still matters for public sites because unauthorized calendar or timetable changes can affect customer trust.
Executive priority
Handle during normal vulnerability remediation unless the plugin controls high-visibility public schedules or critical customer workflows. Escalate if affected admin accounts are broadly used or unmanaged.
Technical view
CVE-2022-45828 is a Cross-Site Request Forgery issue in NooTheme Noo Timetable for WordPress, reported for versions up to 2.1.3. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, low integrity impact, no confidentiality or availability impact. The source bundle does not identify the exact vulnerable action.
Likely exposure
Exposure is limited to WordPress installations that have the Noo Timetable plugin installed at an affected version, reported as 2.1.3 or earlier. Sites without this plugin are not exposed based on the provided sources.
Exploitation context
The CVE is not listed as CISA KEV, and the source bundle provides no evidence of active exploitation. CSRF generally requires a targeted authenticated user to interact with attacker-controlled content, so practical risk depends on admin usage patterns and plugin permissions.
Researcher notes
Evidence is sparse. The CVE and Patchstack entry identify CSRF and affected plugin scope, but not the vulnerable endpoint, action, proof of concept, exploit activity, or fixed version. Avoid assuming broader WordPress compromise from this CVE alone.
Mitigation direction
- Inventory WordPress sites for the Noo Timetable plugin and installed version.
- Check NooTheme, WordPress, or Patchstack guidance for a fixed or safe version.
- Disable or remove the plugin if it is not business-critical.
- Limit administrative sessions to trusted users and managed devices.
Validation and detection
- Confirm whether each WordPress site runs Noo Timetable version 2.1.3 or earlier.
- Review vendor or Patchstack advisories for current remediation status.
- Check recent WordPress admin activity for unexpected timetable or plugin configuration changes.
- Verify affected sites no longer run the vulnerable plugin version after remediation.
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-2022-45828 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
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
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.
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:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
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.