Skip to content

GHSA-rqxp-6926-hphr CVE-2008-1937 PYSEC-2008-12

MoinMoin vulnerable to privilege escalation

High PyPI
Severity
0.0 / 10
High · CVSS 4.0
Exploit chance (EPSS)
1.67%
Chance of exploitation in the next 30 days. Higher than 76.79% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-284 Improper Access Control
Fix
1.6.3
Upgrade moin to this version or later

Description

The user form processing (userform.py) in MoinMoin before 1.6.3, when using ACLs or a non-empty superusers list, does not properly manage users, which allows remote attackers to gain privileges.

Affected versions

PyPI

PackageVulnerableFixed in
moin
< 1.6.3
1.6.3
moin
< 1.6.3
>= 1.7, < 1.7.1
1.6.3
1.7.1

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

moin PyPI → 1.6.3

pip
pip install --upgrade "moin>=1.6.3"
poetry
poetry add "moin>=1.6.3"
uv
uv add "moin>=1.6.3"

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
None
User interaction
None
Confidentiality (vulnerable system)
None
Integrity (vulnerable system)
High
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

CVSS 3.1 7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Weakness

CWE-284: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-cx94-3h5x-cc57
MoinMoin Cross-site scripting (XSS) vulnerability in the antispam feature
Medium Also affects moin
GHSA-7hjm-hqgj-xv9f
MoinMoin Multiple cross-site scripting (XSS) vulnerabilities
Medium Also affects moin
GHSA-jj2f-57jg-5rm6
MoinMoin Improper Access Control
Medium Also affects moin
GHSA-8fj9-pj4p-4vq7
MoinMoin Multiple cross-site scripting (XSS) vulnerabilities
Medium Also affects moin
GHSA-6766-r2rx-mfw9
MoinMoin Directory traversal vulnerability
Medium Also affects moin
GHSA-775g-4482-pm94
MoinMoin Multiple cross-site scripting (XSS) vulnerabilities
Medium Also affects moin
GHSA-53wj-6m7w-j6mj
MoinMoin Cross-site scripting (XSS) vulnerability
Medium Also affects moin
GHSA-cmg7-xr2j-4r9v
MoinMoin Improper ACL handling for calendars and includes
Medium Also affects moin
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor