dbcve.org
MealieApplication

CVE-2022-34621

MEDIUM · 6.5 CVSS v3.1 Published 2022-08-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Mealie 1.0.0beta3 was discovered to contain an Insecure Direct Object Reference (IDOR) vulnerability which allows attackers to modify user passwords and other attributes via modification of the user_id parameter.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Mealie 1.0.0beta3 contains an IDOR vulnerability where authenticated attackers can modify passwords and other attributes of any user by manipulating the user_id parameter in API requests. This broken access control allows unauthorized users to impersonate other users by changing their passwords.

MitigationUpgrade to a patched version of Mealie and implement proper server-side authorization checks to ensure users can only modify their own account data. Validate that the authenticated user matches the requested user_id before processing any modifications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MealieApplication
Affected:= 0.5.5= 1.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Mealie installation and version
    Check the running container or installation for the Mealie version - typically found in docker-compose.yml, container labels, or the application's About/Help page. Run 'docker ps' or check your deployment documentation.
    Affected if The installed version is 0.5.5 or 1.0.0 (exact versions)
  2. Confirm API endpoints are accessible
    Verify that the Mealie API is exposed by attempting to reach the API base URL (commonly /api or /api/docs). Check your reverse proxy or container port mappings.
    Affected if API endpoints are reachable over the network (the vulnerability requires API access)
  3. Verify authentication is enabled
    Check if user registration and login functionality is enabled in Mealie settings. Attempt to log in or check the authentication configuration in the application settings.
    Affected if Authentication is not required or self-registration allows any user to create an account (attackers need valid auth to exploit this)
  4. Review API access controls
    Inspect API requests and responses to confirm whether the application properly validates that the authenticated user matches the user_id being modified. Check server logs for authorization-related errors or warnings.
    Affected if The API allows modifying other users' user_id parameters without proper ownership validation

You are affected if running Mealie version 0.5.5 or 1.0.0, the API is accessible, and users can authenticate - the IDOR allows any authenticated user to modify other users' passwords and attributes by manipulating the user_id parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Mealie and implement proper server-side authorization checks to ensure users can only modify their own account data. Validate that the authenticated user matches the requested user_id before processing any modifications.

Recommended fix Moderate confidence

Latest Mealie release (1.0.0 or later stable version)

  1. 1. Back up your Mealie database and configuration files before updating
  2. 2. Stop the Mealie service
  3. 3. Update Mealie to the latest available version (1.0.0 or higher)
  4. 4. Restart the Mealie service
  5. 5. Verify the application is functioning correctly
  6. 6. Review user accounts to ensure no unauthorized modifications occurred
Caveat Review release notes for any breaking changes between 0.5.5/1.0.0 and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mealie Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34621 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34621 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data