Skip to content
Fencer Intel
critical 9.9

CVE-2022-1810 json

Authorization Bypass Through User-Controlled Key in publify/publify

published 4y ago modified 4mo ago also BIT-publify-2022-1810 , EUVD-2022-3472 , GHSA-c273-c6vg-4pv5

cvss
9.9
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 58%
public exploits
0
none known

Summary

Authorization Bypass Through User-Controlled Key in GitHub repository publify/publify prior to 9.2.9.

Patch / fix

  • rubygems publify_core 9.2.9
  • bitnami publify 9.2.9
  • publify publify/publify 9.2.9

Is CVE-2022-1810 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.84% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • huntr.dev https://huntr.dev/bounties/9b2d7579-032e-42da-b736-4b10a868eacb referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected packages

ecosystem package affected fixed in
rubygems publify_core
<9.2.9
9.2.9
bitnami publify
<9.2.9
9.2.9

Affected products

  • publify publify/publify

Classification

Weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key
  • CWE-284 Improper Access Control
  • CWE-732 Incorrect Permission Assignment for Critical Resource

References

Sources

Fencer Intel 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.