Security readout for executives and security teams
Plain-English summary
This CVE affects the YDS Support Ticket System WordPress plugin through version 1.0. It is a cross-site request forgery issue, meaning a logged-in WordPress user could be tricked into causing unintended actions. The stated impact is limited integrity and availability loss, not data theft.
Executive priority
Treat this as a moderate WordPress hygiene issue. It is not evidenced as actively exploited in the provided sources, but affected sites should be identified and addressed because CSRF can turn normal user browsing into unintended site changes.
Technical view
CVE-2022-36388 is CWE-352 in Ydesignservices YDS Support Ticket System for WordPress <= 1.0. The CVSS 3.1 score is 5.4 with network attack vector, low complexity, no attacker privileges, and required user interaction. Scope is unchanged, confidentiality impact is none, and integrity and availability impacts are low.
Likely exposure
Exposure is limited to WordPress sites that have the YDS Support Ticket System plugin installed at version 1.0 or earlier. The provided sources do not establish broader platform impact, active install counts, or affected configurations beyond that plugin and version range.
Exploitation context
The source bundle does not identify active exploitation, and KEV status is false. The risk depends on convincing an authenticated WordPress user to interact with attacker-controlled content or a malicious link. No exploit details or weaponized public activity are provided in the supplied evidence.
Researcher notes
The public evidence identifies product, version range, CWE, CVSS, and references, but does not provide patch details, proof-of-concept status, or exploitation telemetry. Avoid assuming a fixed version unless confirmed by current vendor or repository guidance.
Mitigation direction
- Inventory WordPress sites for the YDS Support Ticket System plugin.
- Confirm installed plugin versions and flag version 1.0 or earlier.
- Check WordPress.org, Patchstack, and vendor guidance for current remediation status.
- Disable or remove the plugin if unused or unsupported.
- Review WordPress user activity for unexpected plugin-related changes.
Validation and detection
- Verify plugin presence through WordPress asset inventory or administrative plugin listings.
- Record the installed plugin version for each affected site.
- Confirm whether any site runs version 1.0 or earlier.
- Check whether business workflows depend on the plugin before removal.
- Review relevant WordPress logs for unexpected administrative actions.
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-36388 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
- 5.4 (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: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.
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:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/vulnerability/yds-support-ticket-system/wordpress-yds-support-ticket-system-plugin-1-0-cross-site-request-forgery-csrf-vulnerability/_s_id=cveCVE reference · x_refsource_CONFIRM
- https://wordpress.org/plugins/yds-support-ticket-system/CVE reference · x_refsource_CONFIRM
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.