Askbot 0.12.2 - Insecure Direct Object Reference (IDOR)

5.3

Medium

5.3

Medium

Discovered by

Daniel Esteban Celis

External researcher

Summary

Full name

Askbot 0.12.2 - Insecure Direct Object Reference (IDOR) in upload an avatar

Code name

State

Public

Release date

Jan 27, 2026

Affected product

Askbot

Vendor

Askbot

Affected version(s)

0.12.2

Package manager

pypi

Vulnerability name

Insecure object reference

Remotely exploitable

Yes

CVSS v4.0 vector string

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

CVSS v4.0 base score

5.3

Exploit available

No

CVE ID(s)

Description

All versions of askbot before and including 0.12.2 allow an attacker authenticated with normal user permissions to modify the profile picture of other application users. This is possible because the application does not properly validate user authorization when handling profile avatar updates. By intercepting and modifying the POST request used to change the profile picture, an attacker can alter the user_id parameter and update the avatar of any user in the application. The issue occurs in the avatar_view.py file, specifically in the admin_or_owner_require.

Vulnerability

This vulnerability occurs because the application is vulnerable to Insecure Direct Object Reference (IDOR). The admin_or_owner_required function incorrectly validates user permissions by comparing the authenticated user ID with a user_id value supplied by the client, which can be manipulated. As a result, the application fails to enforce proper access control, allowing unauthorized users to perform actions on resources belonging to other users.

PoC

Evidence of Exploitation

Our security policy

We have reserved the ID CVE-2026-1213 to refer to this issue from now on.

Disclosure policy

System Information

  • Askbot

  • Version 0.12.2

  • Operating System: Any

References

Mitigation

An updated version of Askbot is available at the vendor page.

Credits

The vulnerability was discovered by Daniel Celis, an independent security researcher.

Timeline

Jan 2, 2026

Vulnerability discovered

Jan 19, 2026

Vendor contacted

Jan 26, 2026

Vendor replied

Jan 26, 2026

Follow-up with vendor

Jan 26, 2026

Vendor confirmed

Jan 26, 2026

Vulnerability patched

Jan 27, 2026

Public disclosure

Does your application use this vulnerable software?

During our free trial, our tools assess your application, identify vulnerabilities, and provide recommendations for their remediation.

Fluid Attacks' solutions enable organizations to identify, prioritize, and remediate vulnerabilities in their software throughout the SDLC. Supported by AI, automated tools, and pentesters, Fluid Attacks accelerates companies' risk exposure mitigation and strengthens their cybersecurity posture.

Get an AI summary of Fluid Attacks

Subscribe to our newsletter

Stay updated on our upcoming events and latest blog posts, advisories and other engaging resources.

© 2026 Fluid Attacks. We hack your software.

Fluid Attacks' solutions enable organizations to identify, prioritize, and remediate vulnerabilities in their software throughout the SDLC. Supported by AI, automated tools, and pentesters, Fluid Attacks accelerates companies' risk exposure mitigation and strengthens their cybersecurity posture.

Subscribe to our newsletter

Stay updated on our upcoming events and latest blog posts, advisories and other engaging resources.

Get an AI summary of Fluid Attacks

© 2026 Fluid Attacks. We hack your software.

Fluid Attacks' solutions enable organizations to identify, prioritize, and remediate vulnerabilities in their software throughout the SDLC. Supported by AI, automated tools, and pentesters, Fluid Attacks accelerates companies' risk exposure mitigation and strengthens their cybersecurity posture.

Subscribe to our newsletter

Stay updated on our upcoming events and latest blog posts, advisories and other engaging resources.

Get an AI summary of Fluid Attacks

© 2026 Fluid Attacks. We hack your software.