maybe-finance maybe up to 0.6.0 Hostings Controller Synth API key authorization

Summaryinfo

A vulnerability has been found in maybe-finance maybe up to 0.6.0 and classified as critical. Affected is an unknown function of the component Hostings Controller. Performing a manipulation of the argument Synth API key results in authorization. This vulnerability only affects products that are no longer supported by the maintainer. This vulnerability is identified as CVE-2026-63100. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in maybe-finance maybe up to 0.6.0. It has been classified as critical. This affects an unknown part of the component Hostings Controller. The manipulation of the argument Synth API key with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Maybe through 0.6.0 contains a missing authorization vulnerability that allows authenticated low-privilege member-role users to access and modify global hosting settings by exploiting unprotected show and update actions in the Settings::HostingsController, where the before_action ensure_admin filter is applied only to the clear_cache action. Attackers can read the operator's Synth API key rendered in plaintext via a form field value attribute, overwrite it with an attacker-controlled value, toggle public registration settings, and disable email confirmation requirements to disrupt the entire instance.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-63100 since 07/15/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/17/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Financial Software

Vendor

• maybe-finance

Name

• maybe

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6.0

Support

• end of life

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion