Security readout for executives and security teams
Plain-English summary
CVE-2022-47440 affects the WordPress My Tickets plugin through version 1.9.10. It is a CSRF issue, meaning a user could be tricked into causing an unintended action while using a vulnerable site. Reported impact is limited to integrity, with no stated confidentiality or availability impact.
Executive priority
Treat as a moderate-priority WordPress hygiene issue. It is not supported as actively exploited in the provided sources, but ticketing workflows can affect customer operations, so exposed sites should be reviewed and remediated in the normal patch cycle.
Technical view
The source describes CWE-352 CSRF in Joseph C Dolson My Tickets <= 1.9.10. CVSS 3.1 score is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact, no confidentiality or availability impact.
Likely exposure
Exposure is likely limited to WordPress sites running My Tickets plugin <= 1.9.10. Risk depends on whether vulnerable plugin functions are reachable by users who can be induced to interact with attacker-controlled content.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation evidence. CSRF generally requires user interaction and a valid user session, but the provided sources do not describe affected actions, roles, or exploit details.
Researcher notes
Public detail in the bundle is sparse. The CVE identifies plugin, class, version boundary, CWE, and CVSS vector, but does not name vulnerable endpoints, nonce behavior, affected roles, fixed version, or workaround.
Mitigation direction
- Inventory WordPress sites for the My Tickets plugin and version.
- If installed at <= 1.9.10, check vendor or Patchstack guidance for a fixed release.
- Update the plugin when a vendor-supported fixed version is available.
- Disable or remove the plugin where it is not business-critical.
- Limit privileged WordPress sessions on untrusted browsing paths.
Validation and detection
- Confirm plugin presence and exact version on each WordPress site.
- Review vendor and Patchstack entries for current remediation guidance.
- Check whether any public routes depend on My Tickets functionality.
- Verify no affected version remains after update, removal, or compensating action.
- Monitor logs for suspicious state-changing actions involving ticket workflows.
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-47440 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.