AIP-PUB ACPs-community up to 2.2.0 verify-code Endpoint service_auth.py send_verification_code phone improper authentication

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.9$0-$5k0.60+

Summaryinfo

A vulnerability marked as critical has been reported in AIP-PUB ACPs-community up to 2.2.0. This affects the function send_verification_code of the file registry-server/app/account/service_auth.py of the component verify-code Endpoint. The manipulation of the argument phone leads to improper authentication. This vulnerability is listed as CVE-2026-127278. The attack may be initiated remotely. In addition, an exploit is available. The reported GitHub issue was closed with the reason "completed". However, it was not possible to determine the PR or commit which could have fixed this issue.

Detailsinfo

A vulnerability was found in AIP-PUB ACPs-community up to 2.2.0 and classified as critical. This issue affects the function send_verification_code of the file registry-server/app/account/service_auth.py of the component verify-code Endpoint. The manipulation of the argument phone with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality, integrity, and availability.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-127278. 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 as well as a public exploit are known.

The exploit is available at github.com. It is declared as proof-of-concept. The reported GitHub issue was closed with the reason "completed". However, it was not possible to determine the PR or commit which could have fixed this issue.

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

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

Version

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 6.9

VulDB Base Score: 7.3
VulDB Temp Score: 6.9
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Improper authentication
CWE: CWE-287
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

11/12/2026 Advisory disclosed
11/12/2026 +0 days VulDB entry created
11/12/2026 +0 days VulDB entry last update

Sourcesinfo

Product: github.com

Advisory: 11
Status: Confirmed

CNA: VulDB
CVE: CVE-2026-127278 (🔒)

GCVE (CVE): GCVE-0-2026-127278
GCVE (VulDB): GCVE-100-436433
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 11/12/2026 18:34
Changes: 11/12/2026 18:34 (59)
Complete: 🔍
Submitter: Evo1ution
Cache ID: 216::103

Submitinfo

Accepted

  • Submit #1040948: AIP-PUB ACPs-community main @ commit 8334e6b (v2.2.0) Improper Authentication (by Evo1ution)

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!