<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 14:05:11 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-55515</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-55515</link>
      <description>&lt;p&gt;Snipe-IT is an IT asset/license management system. Prior to 8.6.2, the unaccepted-assets report delete endpoint authorizes only reports.view and deletes CheckoutAcceptance::pending()-&amp;gt;find($acceptanceId) by global ID without checking access to the related checkoutable asset, allowing a reports user in one company to delete pending checkout acceptance records for another company. This issue is fixed in version 8.6.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Snipe-IT is an IT asset/license management system. Prior to 8.6.2, the unaccepted-assets report delete endpoint authorizes only reports.view and deletes CheckoutAcceptance::pending()-&amp;gt;find($acceptanceId) by global ID without checking access to the related checkoutable asset, allowing a reports user in one company to delete pending checkout acceptance records for another company. This issue is fixed in version 8.6.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-55515</guid>
    </item>
    <item>
      <title>GHSA-35cr-9hqq-p2mg — Snipe-IT: Cross-company deletion of pending checkout acceptances via unscoped report endpoint</title>
      <link>https://db.gcve.eu/vuln/ghsa-35cr-9hqq-p2mg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: snipe/snipe-it&lt;/p&gt;
&lt;p&gt;### Impact
A user with the `reports.view` permission can delete pending checkout acceptance records by global ID, even when the acceptance belongs to an asset in another company.&lt;/p&gt;
&lt;p&gt;The report listing page appears to scope visible unaccepted assets, but the delete endpoint directly looks up CheckoutAcceptance::pending()-&amp;gt;find($acceptanceId) and deletes it without checking whether the current user has access to the related checkoutable asset.&lt;/p&gt;
&lt;p&gt;### Preconditions
The attacker needs:
- A valid authenticated web session.
- `reports.view` permission.
- Knowledge or guessability of a pending `checkout_acceptances.id`.&lt;/p&gt;
&lt;p&gt;The attacker does not need access to the asset/company associated with the target acceptance.&lt;/p&gt;
&lt;p&gt;### Root cause
The delete action authorizes only report access, then deletes a pending acceptance by global ID:&lt;/p&gt;
&lt;p&gt;```php&lt;/p&gt;
&lt;p&gt;$this-&amp;gt;authorize(&amp;#39;reports.view&amp;#39;);&lt;/p&gt;
&lt;p&gt;$acceptance = CheckoutAcceptance::pending()-&amp;gt;find($acceptanceId);&lt;/p&gt;
&lt;p&gt;$acceptance-&amp;gt;delete();
```&lt;/p&gt;
&lt;p&gt;The code does not check whether the current user can access the acceptance’s related checkoutable asset/accessory/license/etc.
In multi-company mode, this allows a reports user from one company to delete acceptance records belonging to another company.&lt;/p&gt;
&lt;p&gt;### Proof of concept
#### Target acceptance belongs to Company B&lt;/p&gt;
&lt;p&gt;The target pending acceptance was identified as id=1.&lt;/p&gt;
&lt;p&gt;```sql
snipe_sql &amp;#34;SELECT ca.id ca.checkoutable_id, ca.deleted_at, a.asset_tag, a.company_id
FROM checkout_acceptances ca
JOIN assets a ON a.id = ca.checkoutabl…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: snipe/snipe-it&lt;/p&gt;
&lt;p&gt;### Impact
A user with the `reports.view` permission can delete pending checkout acceptance records by global ID, even when the acceptance belongs to an asset in another company.&lt;/p&gt;
&lt;p&gt;The report listing page appears to scope visible unaccepted assets, but the delete endpoint directly looks up CheckoutAcceptance::pending()-&amp;gt;find($acceptanceId) and deletes it without checking whether the current user has access to the related checkoutable asset.&lt;/p&gt;
&lt;p&gt;### Preconditions
The attacker needs:
- A valid authenticated web session.
- `reports.view` permission.
- Knowledge or guessability of a pending `checkout_acceptances.id`.&lt;/p&gt;
&lt;p&gt;The attacker does not need access to the asset/company associated with the target acceptance.&lt;/p&gt;
&lt;p&gt;### Root cause
The delete action authorizes only report access, then deletes a pending acceptance by global ID:&lt;/p&gt;
&lt;p&gt;```php&lt;/p&gt;
&lt;p&gt;$this-&amp;gt;authorize(&amp;#39;reports.view&amp;#39;);&lt;/p&gt;
&lt;p&gt;$acceptance = CheckoutAcceptance::pending()-&amp;gt;find($acceptanceId);&lt;/p&gt;
&lt;p&gt;$acceptance-&amp;gt;delete();
```&lt;/p&gt;
&lt;p&gt;The code does not check whether the current user can access the acceptance’s related checkoutable asset/accessory/license/etc.
In multi-company mode, this allows a reports user from one company to delete acceptance records belonging to another company.&lt;/p&gt;
&lt;p&gt;### Proof of concept
#### Target acceptance belongs to Company B&lt;/p&gt;
&lt;p&gt;The target pending acceptance was identified as id=1.&lt;/p&gt;
&lt;p&gt;```sql
snipe_sql &amp;#34;SELECT ca.id ca.checkoutable_id, ca.deleted_at, a.asset_tag, a.company_id
FROM checkout_acceptances ca
JOIN assets a ON a.id = ca.checkoutabl…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-35cr-9hqq-p2mg</guid>
    </item>
  </channel>
</rss>
