IXP Manager has Broken Object-Level Authorization
Affects IXP Manager versions before 7.3.0, where an authenticated user can view and edit another user's resources without authorisation. Fixed in 7.3.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 7.3.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
IXP Manager, a web application used to manage Internet Exchange Points, is affected by a flaw that lets any logged-in user view and modify another user's API key records. An attacker with a valid account could therefore read and change credentials belonging to other users, potentially gaining unauthorized access to their functions.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
IXP Manager is a full-stack web application for managing Internet Exchange Points. Prior to version 7.3.0, an authenticated user can view and edit a resource belonging to another user without authorization. The API-key edit/update path in `ApiKeyController` selects records by identifier without checking that `user_id` matches the caller, allowing access to another user's API-key record. This issue is fixed in version 7.3.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- inex IXP-Manager
fixed in 7.3.0
References 3
GitHub · inex/IXP-Manager
Questions about CVE-2026-63338
What does this mean?
An authenticated user could view and edit a resource that belongs to another user, without the authorisation that should block that access.Source: github.com
Am I affected, and how do I check?
IXP Manager versions before 7.3.0 are affected, and the issue requires an authenticated user account. To check, compare the IXP Manager version in use with 7.3.0.Source: github.com
What should I do about it?
Upgrade IXP Manager to v7.3.0 as soon as possible. The advisory says this release addresses the issue.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data