Skip to content
Fencer Vulns
low 3.5

CVE-2022-0088 json

Cross-Site Request Forgery (CSRF) in yourls/yourls

published 2022-04-03 4 y ago modified 2026-06-17 4 mo ago also GHSA-gx7g-wjxg-jwwj , EUVD-2022-1750

cvss
3.5
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 80%
public exploits
1
Exploit-DB

Summary

Cross-Site Request Forgery (CSRF) in GitHub repository yourls/yourls prior to 1.8.3.

Patch / fix

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-0088 updated cvss 7.4

yourls: CSRF may trick user to logout

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. Published
  2. First public exploit (EDB-52446)

Exploit prediction

1.99% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-52446 YOURLS 1.8.2 - Cross-Site Request Forgery (CSRF) webapps, 2025-12-02
  • huntr.dev https://huntr.dev/bounties/d01f0726-1a0f-4575-ae17-4b5319b11c29 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 3.5 CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
NVD 3.1 7.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N
GitHub 3.0 3.5 CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
packagist yourls/yourls
<=1.8.2
no fix listed

Affected products

  • yourls yourls/yourls

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.