Security readout for executives and security teams
Plain-English summary
This vulnerability affects the WP ULike WordPress plugin and can let unauthenticated visitors manipulate like or rating scores through a race condition. It does not indicate data theft or service outage, but it can damage trust in site engagement metrics and user-facing reputation signals.
Executive priority
Prioritize this where ratings, likes, testimonials, or popularity metrics influence customer trust, sales, or moderation decisions. It is not a critical breach indicator, but public-facing metric manipulation can create reputational and operational risk.
Technical view
CVE-2022-45842 is a CWE-367 race condition in WP ULike for WordPress, described as affecting versions up to 4.6.4. The CVSS 3.1 score is 5.3 with network access, low complexity, no privileges, no user interaction, and low integrity impact only.
Likely exposure
Exposure is most likely on public WordPress sites running WP ULike where unauthenticated users can submit likes, dislikes, ratings, or similar engagement actions.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The issue is unauthenticated and low complexity, but the documented impact is limited to increasing or decreasing rating scores.
Researcher notes
The bundle describes affected versions as <=4.6.4, while the Patchstack URL title references 4.6.3. Treat the exact fixed boundary as unconfirmed from the provided evidence. No exploit code, patch version, or active exploitation evidence is included in the supplied sources.
Mitigation direction
- Inventory WordPress sites for WP ULike and record installed versions.
- Check TechnoWich or Patchstack guidance for the fixed version before relying on updates.
- Upgrade WP ULike only when vendor guidance identifies a non-vulnerable release.
- Temporarily disable affected rating features where score integrity is business-critical.
- Restrict or monitor unauthenticated engagement actions if disabling is not feasible.
Validation and detection
- Confirm whether WP ULike is installed on each WordPress site.
- Compare installed plugin versions with the CVE-described affected range.
- Review public pages for unauthenticated like or rating functionality.
- Check rating histories for abnormal score changes or sudden bursts.
- Document any uncertainty caused by conflicting affected-version references.
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-367: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-45842 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.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:N/S:U/C:N/I:L/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/vulnerability/wp-ulike/wordpress-wp-ulike-plugin-4-6-3-race-condition-vulnerability?_s_id=cveCVE reference · vdb-entry
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.
Time-of-check Time-of-use (TOCTOU) Race Condition
Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.