dbcve.org
FlygoApplication · Larvata

CVE-2021-37212

MEDIUM · 5.4 CVSS v3.1 Published 2021-08-09
Fix available
A fix is available. Upgrade to 1.91.1 or later.
See remediation →
60/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
The bulletin function of Flygo contains Insecure Direct Object Reference (IDOR) vulnerability. After being authenticated as a general user, remote attackers can manipulate the bulletin ID in specific Url parameters and access and modify bulletin particular content.

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

Flygo bulletin function contains an Insecure Direct Object Reference (IDOR) vulnerability where authenticated general users can manipulate bulletin ID parameters in URLs to access and modify bulletins they should not have permission to view or edit. This represents a vertical privilege escalation allowing regular users to bypass authorization on bulletin resources.

MitigationImplement proper object-level authorization checks to verify the requesting user has permission to access or modify the specific bulletin ID before returning or altering any content. Enforce access control at the application layer for all bulletin operations.

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
FlygoApplication
Affected:< 1.91.1

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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. Confirm Larvata Flygo installation and version
    Locate the Flygo application installation directory and identify the version file or metadata. Common locations include version.rb, package.json, or the application's about page in the web interface. Compare the installed version to the affected range: versions prior to 1.91.1 are vulnerable.
    Affected if The installed version of Larvata Flygo is lower than 1.91.1.
  2. Verify bulletin module is enabled
    Access the Flygo administrative console or configuration files to confirm the bulletin function module is active. Check application configuration files (config/settings.yml, config/application.rb, or similar) for bulletin-related feature flags.
    Affected if The bulletin module is enabled and accessible to general users.
  3. Examine user role permissions for bulletins
    Review the application's user role and permission configuration. Access the admin panel to view role definitions for 'general' or 'standard' users. Look for bulletin-related permission entries and verify if general users have any bulletin access permissions assigned.
    Affected if General users have been granted any bulletin create, read, update, or delete permissions.
  4. Test bulletin IDOR vulnerability
    Using an authenticated general (non-admin) user account, attempt to access bulletin URLs by manipulating the bulletin ID parameter. For example, if bulletins are accessed at /bulletins/{id}, try accessing IDs that would belong to other users or admin-created bulletins. Observe whether the application returns content or allows modifications without proper authorization checks.
    Affected if The application returns bulletin content or allows modifications for bulletin IDs that the test user should not have access to based on the role permissions.
  5. Review application logs for unauthorized bulletin access
    Examine Flygo application logs (typically in logs/ directory) for bulletin-related requests. Search for patterns where general users access bulletin endpoints with IDs outside their expected scope. Look for successful responses (HTTP 200) on GET/PUT/DELETE requests to /bulletins/{id} for IDs not owned by the requesting user.
    Affected if Logs show successful bulletin access or modification requests by general users on bulletins outside their assigned permissions.

A user is affected if running Larvata Flygo version below 1.91.1 with the bulletin module enabled and general users can access or modify bulletins via ID parameter manipulation.

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.

From vendor data
Upgrade available Upgrade to 1.91.1 or later
Fixed in 1.91.1
Interim mitigation

Implement proper object-level authorization checks to verify the requesting user has permission to access or modify the specific bulletin ID before returning or altering any content. Enforce access control at the application layer for all bulletin operations.

Fix this in Flygo 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 the upgrade done

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-2021-37212 — 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-2021-37212 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