Timetable And Event ScheduleWordPress extension · Motopress
CVE-2022-2844
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 · uneditedA vulnerability classified as problematic has been found in MotoPress Timetable and Event Schedule up to 1.4.06. This affects an unknown part of the file /wp/?cpmvc_id=1&cpmvc_do_action=mvparse&f=datafeed&calid=1&month_index=1&method=adddetails&id=2 of the component Calendar Handler. The manipulation of the argument Subject/Location/Description leads to cross site scripting. It is possible to initiate the attack remotely. The associated identifier of this vulnerability is VDB-206487.
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 stored cross-site scripting (XSS) vulnerability exists in the MotoPress Timetable and Event Schedule WordPress plugin (up to v1.4.06). The Calendar Handler component fails to properly sanitize user-supplied input in the Subject, Location, and Description fields when processing requests to /wp/?cpmvc_id=1&cpmvc_do_action=mvparse&f=datafeed&calid=1&month_index=1&method=adddetails&id=2, allowing authenticated or remote attackers to inject malicious JavaScript that executes in victim browsers.
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
Timetable And Event ScheduleWordPress extension
<= 1.4.06CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installation and versionNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Locate 'MotoPress Timetable and Event Schedule' and note the installed version number.Affected if The plugin is installed and the version is 1.4.06 or lower.
-
Identify vulnerable endpoint accessibilityVerify the plugin's calendar functionality is active by accessing the datafeed endpoint at /wp/?cpmvc_id=1&cpmvc_do_action=mvparse&f=datafeed&calid=1. Check if this returns a valid response.Affected if The calendar datafeed endpoint is accessible and responds without authentication errors.
-
Check for existing XSS entries in calendar fieldsQuery the WordPress database posts table for any records containing the motopress_timetable post type (or custom post type used by the plugin). Inspect the Subject, Location, and Description fields for suspicious script tags or javascript: URIs.Affected if Any calendar event entries contain unescaped HTML script tags or event handlers in Subject, Location, or Description fields.
-
Verify user input acceptance in calendar formAccess the calendar event submission form (typically at /wp/?cpmvc_id=1&cpmvc_do_action=mvparse&f=adddetails or via the frontend calendar interface). Submit a test event with <script>alert('XSS')</script> in the Subject, Location, and Description fields.Affected if The submitted test payload is stored and rendered without being escaped or sanitized when the event is displayed.
You are affected if the MotoPress Timetable plugin version is 1.4.06 or lower and the calendar datafeed endpoint is accessible without additional access controls.
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 MotoPress Timetable and Event Schedule to the latest patched version; as an interim measure, deploy a WAF rule to filter or block malicious payloads in the affected parameters, and restrict access to the vulnerable endpoint.
Fix this in Timetable And Event Schedule
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2844 — 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-2022-2844 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