Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.3

Froxlor vulnerable to Cross-Site Request Forgery

CVE-2022-4867GHSA-6gwx-gw56-qhf7

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (froxlor/froxlor 2.0.0-beta1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist froxlor/froxlor

    Affected
    >= 2.0.0-beta0, < 2.0.0-beta1
    Fixed in
    2.0.0-beta1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
EPSS
  • CVE-2022-4867: 0.37% estimated exploitation activity in the next 30 days; percentile 30.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Cross-Site Request Forgery (CSRF) in GitHub repository froxlor/froxlor prior to 2.0.0-beta1.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-6gwx-gw56-qhf7

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-4867

Advisory: Froxlor vulnerable to Cross-Site Request Forgery
IDs: CVE-2022-4867, GHSA-6gwx-gw56-qhf7
Record: https://patchnext.com/advisories/cve-2022-4867 (revision 1, source checked 26 Oct 2026, 14:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: froxlor/froxlor 2.0.0-beta1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist froxlor/froxlor: affected >= 2.0.0-beta0, < 2.0.0-beta1; fixed in 2.0.0-beta1

## Suggested inspection (read-only)
- Packagist froxlor/froxlor: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on froxlor/froxlor.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6gwx-gw56-qhf7 (GitHub-reviewed advisory GHSA-6gwx-gw56-qhf7 lists affected ranges: Packagist froxlor/froxlor >=2.0.0-beta0 <2.0.0-beta1)

Commands are suggestions: review each one before running it.

Loading voting…