Skip to main content
No exploitation reportedFix available

CVE-2022-1681

No exploitation reported by the sources we read.

  • Published2022-05-12
  • Fixed in2.5.281
  • WeaknessCWE-287 · CWE-288

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Authentication Bypass Using an Alternate Path or Channel in GitHub repository requarks/wiki prior to 2.5.281. User can get root user permissions

Timeline

dates in UTC
  1. 2022-05-1208:15CVE publishedNVD

Versions per branch

NVD
Requarks wiki.js
BranchAffectedFixed in
2.5< 2.5.2812.5.281

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Requarks wiki.js to 2.5.281

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVSS 3.17.2read 2026-10-23
  • CNACVSS 3.07.2known since 2026-10-23
  • NVDCVSS 2.09read 2026-10-23
  • CNAweakness (CWE)CWE-288known since 2026-10-23
  • NVDweakness (CWE)CWE-287read 2026-10-23
  • FIRST EPSSEPSS score2.0 %2026-11-08
  • GitHub Advisoriesadvisory—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Published
2022-05-12
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-mrfc-q2c7-f9ww

Frequently asked questions

What is CVE-2022-1681?

Authentication Bypass Using an Alternate Path or Channel in GitHub repository requarks/wiki prior to 2.5.281. User can get root user permissions

Is CVE-2022-1681 actively exploited?

Active exploitation of CVE-2022-1681 has not been confirmed. Its EPSS score was 2.0% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-1681?

CVE-2022-1681 has a CVSS v3 base score of 7.2 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record