fossasia open-event-server 1.19.1 Mail Verification mail.py send_email_change_user_email reliance on obfuscation or encryption of security-relevant inputs without integrity checking

Summaryinfo

A vulnerability, which was classified as critical, has been found in fossasia open-event-server 1.19.1. The impacted element is the function send_email_change_user_email of the file /fossasia/open-event-server/blob/development/app/api/helpers/mail.py of the component Mail Verification Handler. The manipulation leads to reliance on obfuscation or encryption of security-relevant inputs without integrity checking. This vulnerability is listed as CVE-2025-5323. The attack may be initiated remotely. In addition, an exploit is available. The vendor was contacted early about this disclosure but did not respond in any way.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in fossasia open-event-server 1.19.1. This issue affects the function send_email_change_user_email of the file /fossasia/open-event-server/blob/development/app/api/helpers/mail.py of the component Mail Verification Handler. The manipulation with an unknown input leads to a reliance on obfuscation or encryption of security-relevant inputs without integrity checking vulnerability. Using CWE to declare the problem leads to CWE-649. The product uses obfuscation or encryption of inputs that should not be mutable by an external actor, but the product does not use integrity checks to detect if those inputs have been modified. Impacted is integrity.

The advisory is shared at gist.github.com. The identification of this vulnerability is CVE-2025-5323. The exploitation is known to be difficult. 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 gist.github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.

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

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

Productinfo

Vendor

Name

Version

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.7
VulDB Meta Temp Score: 3.5

VulDB Base Score: 3.7
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 3.7
CNA Vector: 🔒

CVSSv2info

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

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

Exploitinginfo

Class: Reliance on obfuscation or encryption of security-relevant inputs without integrity checking
CWE: CWE-649 / CWE-325
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒

EPSS Score: 🔒
EPSS Percentile: 🔒

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

05/29/2025 Advisory disclosed
05/29/2025 +0 days VulDB entry created
05/30/2025 +1 days VulDB entry last update

Sourcesinfo

Advisory: gist.github.com
Status: Not defined

CVE: CVE-2025-5323 (🔒)
GCVE (CVE): GCVE-0-2025-5323
GCVE (VulDB): GCVE-100-310493
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 05/29/2025 10:25
Updated: 05/30/2025 09:02
Changes: 05/29/2025 10:25 (57), 05/30/2025 09:02 (30)
Complete: 🔍
Submitter: Gavin Zhong
Cache ID: 216::103

Submitinfo

Accepted

  • Submit #580256: open-event-server v1.19.1 Reliance on Obfuscation or Encryption of Security-Relevant Input (by Gavin Zhong)

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!