CVE-2025-13480 | Fudo Security Fudo Enterprise up to 5.6.2 API Endpoint authorization
VulDBArchived Apr 20, 2026✓ Full text saved
A vulnerability was found in Fudo Security Fudo Enterprise up to 5.6.2 . It has been classified as problematic . Affected by this issue is some unknown functionality of the component API Endpoint . Performing a manipulation results in incorrect authorization. This vulnerability was named CVE-2025-13480 . The attack needs to be approached within the local network. There is no available exploit. Upgrading the affected component is recommended.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-358294 · CVE-2025-13480 · GCVE-0-2025-13480
FUDO SECURITY FUDO ENTERPRISE UP TO 5.6.2 API ENDPOINT AUTHORIZATION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
3.4 $0-$5k 2.90+
Summaryinfo
A vulnerability was found in Fudo Security Fudo Enterprise up to 5.6.2. It has been declared as problematic. This affects an unknown part of the component API Endpoint. Executing a manipulation can lead to authorization. The identification of this vulnerability is CVE-2025-13480. The attack needs to be done within the local network. There is no exploit available. It is recommended to upgrade the affected component.
Detailsinfo
A vulnerability has been found in Fudo Security Fudo Enterprise up to 5.6.2 and classified as problematic. This vulnerability affects some unknown processing of the component API Endpoint. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. As an impact it is known to affect confidentiality. CVE summarizes:
Fudo Enterprise in versions from 5.5.0 through 5.6.2 allows low privileged users to access certain administrator-only resources via improperly protected API endpoints. This includes sensitive information such as system logs and parts of system configuration settings. This vulnerability has been fixed in version 5.6.3
The advisory is available at fudosecurity.com. This vulnerability was named CVE-2025-13480 since 11/20/2025. The exploitation appears to be easy. Access to the local network is required for this attack to succeed. The technical details are unknown and an exploit is not available.
Upgrading to version 5.6.3 eliminates this vulnerability.
Productinfo
Vendor
Fudo Security
Name
Fudo Enterprise
Version
5.6.0
5.6.1
5.6.2
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 3.5
VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Authorization
CWE: CWE-863 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: Fudo Enterprise 5.6.3
Timelineinfo
11/20/2025 CVE reserved
04/20/2026 +150 days Advisory disclosed
04/20/2026 +0 days VulDB entry created
04/20/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: fudosecurity.com
Status: Confirmed
CVE: CVE-2025-13480 (🔒)
GCVE (CVE): GCVE-0-2025-13480
GCVE (VulDB): GCVE-100-358294
Entryinfo
Created: 04/20/2026 11:52
Changes: 04/20/2026 11:52 (66)
Complete: 🔍
Cache ID: 99:EE4:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸