dbcve.org
Noo TimetableWordPress extension · Nootheme

CVE-2022-45821

MEDIUM · 5.4 CVSS v3.1 Published 2023-08-08
Fix available
A fix is available. Upgrade to after 2.1.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in NooTheme Noo Timetable plugin <= 2.1.3 versions.

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 confidence

Stored Cross-Site Scripting (XSS) vulnerability in the NooTheme Noo Timetable WordPress plugin affecting versions 2.1.3 and below. Authenticated users with contributor-level or higher privileges can inject malicious JavaScript that persists on the server and executes when other users view the compromised content.

MitigationUpdate the NooTheme Noo Timetable plugin to the latest version beyond 2.1.3. If no update is available, disable the plugin and implement input sanitization (esc_html/esc_attr) and output encoding at all user-input handling points in the code.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Noo TimetableWordPress extension
Affected:<= 2.1.3

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Noo Timetable plugin is installed
    Access WordPress admin panel, go to Plugins > Installed Plugins, and look for 'Nootheme Noo Timetable' in the list. Alternatively, check the plugin directory at /wp-content/plugins/noo-timetable/ for the existence of plugin files.
    Affected if The plugin is installed and active in WordPress.
  2. Determine installed plugin version
    In WordPress admin, find the Noo Timetable entry in the Plugins list and read the version number displayed beneath the plugin name. Alternatively, open the main plugin file (e.g., noo-timetable.php) and look for the 'Version' header in the file comments.
    Affected if The version is 2.1.3 or lower.
  3. Check for users with contributor-level or higher access
    In WordPress admin, navigate to Users > All Users and review the role column. Look for users assigned roles of Contributor, Author, Editor, or Administrator. Alternatively, query the wp_usermeta table for user_role_capabilities containing 'contributor', 'author', 'editor', or 'administrator' capabilities.
    Affected if At least one user account has contributor-level privileges or higher, enabling them to create timetable content.
  4. Identify timetable content entries
    Check for any events, schedules, or timetable entries created using the Noo Timetable plugin. Access the custom post types added by the plugin (typically under a Timetable menu in admin) or query the wp_posts table for post types associated with the plugin.
    Affected if Timetable content exists in the database, as this represents potential storage locations for malicious script injection.

If the Noo Timetable plugin version is 2.1.3 or lower, an authenticated user with contributor-level or higher privileges exists, and timetable content has been created, the environment is likely affected by this stored XSS vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.1.3
Interim mitigation

Update the NooTheme Noo Timetable plugin to the latest version beyond 2.1.3. If no update is available, disable the plugin and implement input sanitization (esc_html/esc_attr) and output encoding at all user-input handling points in the code.

Fix this in Noo Timetable Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45821 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-45821 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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