WWBN AVideo up to 30.0 MobileManager Plugin getConfiguration.json.php information disclosure

Summaryinfo

A vulnerability classified as problematic has been found in WWBN AVideo up to 30.0. This affects an unknown part of the file plugin/MobileManager/getConfiguration.json.php of the component MobileManager Plugin. The manipulation leads to information disclosure. This vulnerability is traded as CVE-2026-84481. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in WWBN AVideo up to 30.0 and classified as problematic. This issue affects some unknown processing of the file plugin/MobileManager/getConfiguration.json.php of the component MobileManager Plugin. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:

WWBN AVideo through 30.0 contains an information disclosure vulnerability in the MobileManager plugin getConfiguration endpoint that returns sensitive configuration data to unauthenticated visitors. Attackers can send an unauthenticated GET request to plugin/MobileManager/getConfiguration.json.php to obtain TLS private key file paths, socket configuration details, platform version, and debug flags enabling further targeted attacks.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-84481 since 09/01/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/02/2026). MITRE ATT&CK project uses the attack technique T1592 for this issue.

By approaching the search of inurl:plugin/MobileManager/getConfiguration.json.php it is possible to find vulnerable targets with Google Hacking.

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

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-69723). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• WWBN

Name

• AVideo

Version

• 30.0

License

• open-source

Website

• Product: https://github.com/WWBN/AVideo/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion