Permissive parameters and privilege escalation

published 2018-12-20 7y ago modified 2026-06-17 4mo ago also GHSA-mrq8-53r4-3j5m , EUVD-2022-1108

cvss: 6.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.9%; EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits: 0; none known

An issue was discovered in Steve Pallen Coherence before 0.5.2 that is similar to a Mass Assignment vulnerability. In particular, "registration" endpoints (e.g., creating, editing, updating) allow users to update any coherence_fields data. For example, users can automatically confirm their accounts by sending the confirmed_at parameter with their registration request.

Patch / fix

fixed in 2

hex coherence 0.5.2
coherence_project coherence 0.5.2

Is CVE-2018-20301 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.90% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem	package	affected	fixed in
hex	coherence	<0.5.2	0.5.2

Classification

Weakness

CWE-20 Improper Input Validation

References

github.com /smpallen99/coherence/issues/270
web, issue-tracking, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2018-20301
advisory
github.com /smpallen99/coherence
package

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.