目标达成 感谢每一位支持者 — 我们达成了 100% 目标!

目标: 1000 元 · 已筹: 1336

100%

CVE-2025-50341 PoC — Axelor 安全漏洞

来源
关联漏洞
标题: Axelor 安全漏洞 (CVE-2025-50341)
Description:Axelor是法国Axelor公司的一个模块化开发框架。 Axelor 5.2.4版本存在安全漏洞,该漏洞源于_domain参数存在布尔型SQL注入,可能导致数据泄露。
Description
Public advisory for CVE-2025-50341 in Axelor
介绍
# CVE-2025-50341: Sql Injection on Axelor

CVE ID: CVE-2025-50341  
Reporter: Milad Seddigh  
Product: Axelor  
Affected Versions: v5.2.4  
Impact: Sql Injection → exfiltrating database content. 

## Summary

A Boolean-based SQL injection vulnerability was discovered in the “_domain” parameter of the Axelor. An attacker 
can manipulate the SQL query logic and determine true/false conditions, potentially leading to data exposure or further 
exploitation. 

## Steps to Reproduce

1- Login to your account. 
2- Intercept the requests that include the “_domain” parameter in the body. 
3- Insert a Boolean payload (or 1=1) in the “domain” parameter. 
4- Insert a Boolean payload (or 1=2) in the “domain” parameter. 
5- Observe the difference in server response for when 1=1 and 1=2. 
6- Dump all database contents.

## Mitigation

1. Use Parameterized Queries / Prepared Statements
Ensure that all SQL queries are constructed using parameterized statements or prepared queries. This approach separates SQL logic from user input and prevents injection.
2. Employ ORM Libraries (Where Appropriate)
Using modern ORM (Object-Relational Mapping) libraries (e.g., Sequelize, Prisma, TypeORM) can help abstract raw SQL and enforce safe query practices.
3. Validate and Sanitize Input
Enforce strict input validation based on context (e.g., numeric ID must only contain digits).
Reject or sanitize inputs that do not meet expected format.
Use allow-lists rather than block-lists for validation.
文件快照

登录后查看神龙缓存的 POC 文件快照

登录查看
备注
    1. 建议优先通过来源进行访问。
    2. 本地 POC 快照面向订阅用户开放;当原始来源失效或无法访问时,本地镜像作为订阅权益的一部分提供。
    3. 持续抓取、验证、维护这份 POC 档案需要不少投入,因此本地快照已纳入付费订阅。您的订阅是让这份资料能继续走下去的关键,由衷感谢。 查看订阅方案 →