NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
HIGH severity

Froxlor Incorrect Access ControlGHSA-r6g8-mq9v-cgp4

HIGHFix: Froxlor/Froxlor@aa88156

GHSA-r6g8-mq9v-cgp4 is a high-severity (CVSS 7.5) CWE-732 vulnerability in froxlor/froxlor. A fix is available for froxlor/froxlor — see the affected versions and patch details below.

Also known asCVE-2018-12642
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk
0.00%0.63%1.27%1.90%0.3%1.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐘froxlor/froxlor

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Froxlor through 0.9.39.5 has Incorrect Access Control for tickets not owned by the current user.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistfroxlor/froxlorall versions0.9.40composer require froxlor/froxlor:^0.9.40

Affected Products

1 product · 1 configurations
Application
froxlorfroxlor
≤ 0.9.39.5
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for froxlor/froxlor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update froxlor/froxlor to 0.9.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r6g8-mq9v-cgp4 is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Froxlor through 0.9.39.5 has Incorrect Access Control for tickets not owned by the current user.
O3 Security · Impact-Aware SCA

Is GHSA-r6g8-mq9v-cgp4 in your dependencies?

Find it across Packagist, including transitive dependencies.

Froxlor Incorrect Access Control (High 7.5)