Skip to main content

Sure CVE-2026-110772

| EUVDEUVD-2026-101572 MEDIUM
Missing Authorization (CWE-862)
2026-10-14 disclosure@vulncheck.com GHSA-v84h-gfv8-x79x
5.3
CVSS 4.0 · Vendor: vulncheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privilege family member
  2. Delivery
    Enumerate/guess other members' entry_ids
  3. Exploit
    Craft bulk-update request to BulkUpdatesController#create
  4. Execution
    Submit arbitrary entry_ids bypassing authorization
  5. Persist
    Overwrite other members' transaction fields
  6. Impact
    Corrupt budgets and financial reports

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated account inside a Sure instance that uses account sharing with multiple family members; the attacker's account need only have read_only or no share privilege (PR:L). The attacker must be able to reach the bulk-updates endpoint and supply entry_ids belonging to other members - the missing authorization check is the enabling condition, present by default in affected versions where sharing is used. Limiting factors: single-user instances and instances without shared accounts are not exploitable, the attacker needs valid authenticated credentials in the same family, and impact is confined to integrity of transaction metadata (no data disclosure, no service disruption). No end-user interaction from the victim is required.

Impact

This is a medium-severity authorization flaw (CWE-862) whose signals are internally consistent and point to a real but bounded risk. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) indicates remote, low-complexity exploitation by an already-authenticated low-privilege user, with impact limited to integrity of one component (VI:L) and no confidentiality or availability loss (VC:N/VA:N) - matching the description, where read_only or no-share family members can alter other members' transaction metadata but cannot read protected data or crash the service. No EPSS score was provided, the CVE is not on CISA KEV, and no proof-of-concept exploit flag is present in the input, so there is no public exploit identified at time of analysis. The PR:L requirement is the single biggest risk-limiter: an attacker already needs a legitimate account inside the same family/shared instance, making this an insider/abuse-of-trust problem rather than an internet-facing mass-exploitation threat. The low score and absence of exploitation signals are congruent - this is a genuine broken-access-control bug worth patching for multi-user deployments, but it is not an emergency-priority issue. Note one metadata conflict: the single tag 'Authentication Bypass' contradicts the description and CWE-862, which describe an authorization (not authentication) bypass by an already-authenticated user.

Exploit ScenarioDerived

In a shared Sure instance, a family member who was granted read-only access (or no sharing at all) crafts a request to the Transactions::BulkUpdatesController#create endpoint supplying entry_ids that belong to other members. Because the controller fails to verify the caller is authorized for those entries, the attacker silently rewrites the dates, names, notes, categories, merchants, and tags of other members' transactions, corrupting their budgets and reports. No public exploit is identified in the provided data, but the attack requires only a standard authenticated request with low complexity.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

Authenticated users with read-only or no share permission in Sure 0.7.0 through 0.7.6-alpha.6 can silently alter other family members' transactions - dates, names, notes, categories, merchants and tags - by submitting arbitrary entry_ids to the Transactions::BulkUpdatesController#create action, which performs no ownership or authorization check on the supplied records. It is a medium-severity missing authorization flaw (CWE-862, assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) that corrupts budgets and reports for the victim accounts but causes no data disclosure or service disruption, and it only applies where account sharing among multiple family members is in use. Exploitation requires valid low-privileged credentials in the same instance; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis.

RemediationAI

No vendor-released patch version is identified in the available data, so the first step is to confirm whether an upstream fix has landed by monitoring https://github.com/we-promise/sure/issues/2099, the repository history referenced at https://github.com/we-promise/sure/blob/a3bb5d991f9b96e335e9212b1a6324289577f143/app/controllers/transactions/bulk_updates_controller.rb#L5-L13, and the advisory at https://www.vulncheck.com/advisories/sure-0.7.0-through-0.7.6-alpha.6-missing-authorization-via-transaction-bulk-update, then upgrade to the first release that adds an ownership check on entry_ids. Until such a release is verified, the most effective compensating control is to stop using account sharing: remove non-owner members or run a separate Sure instance per user, which fully removes the attack path at the cost of losing the collaborative budgeting workflow. If sharing must remain, limit membership to fully trusted individuals, treat every read_only or no-share account as able to tamper with other members' transaction metadata, and take database backups before granting new shares so corrupted budgets and reports can be restored. A reverse-proxy or WAF rule that blocks POST requests to the bulk-updates endpoint from sessions belonging to read_only or no-share members adds a second layer, but it is brittle because it depends on session-to-role mapping outside the application and will break if routes or role handling change; log and alert on bulk-update calls that reference entry_ids not owned by the requesting user so tampering is detected even when it cannot be prevented.

Affected VersionsENISA

sure 0.7.0 ≤0.7.6-alpha.6

Affected Packages

euvd sure no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Sure is a self-hosted Ruby on Rails personal-finance and budgeting application that supports account sharing between family members, with roles that include full access, read_only, and no share at all. The affected code path is the bulk-updates endpoint in app/controllers/transactions/bulk_updates_controller.rb (lines 5-13 in commit a3bb5d991f9b96e335e9212b1a6324289577f143), which accepts a caller-supplied list of entry_ids and applies attribute changes to the corresponding Transaction records. The controller relies on authentication and on the caller's role being enforced elsewhere, but never verifies that the entry_ids belong to the requesting user or to a share the user is permitted to write - the classic CWE-862 Missing Authorization pattern of pairing authentication with an object reference the server does not re-authorize (an IDOR-style failure in a Rails controller action). Because the endpoint is reachable over the network with an ordinary session and no victim interaction, the NVD CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N) and the independently assessed CVSS 3.1 vector agree that confidentiality and availability are unaffected while integrity of transaction metadata is partially compromised; PR:L confirms the attacker must hold an authenticated account, though that account can be the least-privileged member of the shared family.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vulncheck) PRIMARY 5.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
vuln.today AI 4.3 MEDIUM

Remote web endpoint (AV:N) abused by an authenticated low-privilege member (PR:L) with no user interaction; only integrity of transaction data is affected (I:L), no C/A impact and no scope change.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Red Hat 4.3 MEDIUM

Primary rating from Vendor (vulncheck).

CVSS VectorVendor: vulncheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Sure 0.7.0 through 0.7.6-alpha.6 contains a missing authorization vulnerability in Transactions::BulkUpdatesController#create that allows family members to bypass account sharing permissions. Authenticated members with read_only or no share can submit arbitrary entry_ids to modify other members' transaction dates, names, notes, categories, merchants and tags, corrupting budgets and reports.

Threat Intelligence Overview

EPSS Score
0.3%
Top 83% exploitable
Prevalence
Low
self-hosted open-source personal-finance app, niche hobbyist footprint
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment Vendor GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy