Skip to content

New vulnerability module for Triofox CVE-2025-12480 detection - #1237

Open
Aarush289 wants to merge 8 commits into
OWASP:masterfrom
Aarush289:CVE-2025-12480
Open

New vulnerability module for Triofox CVE-2025-12480 detection#1237
Aarush289 wants to merge 8 commits into
OWASP:masterfrom
Aarush289:CVE-2025-12480

Conversation

@Aarush289

@Aarush289 Aarush289 commented Jan 22, 2026

Copy link
Copy Markdown
Contributor

Proposed change

This PR adds a new vulnerability detection module for CVE-2025-12480, an improper access control vulnerability affecting Gladinet Triofox.

The vulnerability allows unauthenticated users to access restricted administrative or setup endpoints due to missing or insufficient access control checks. The module detects this issue by sending an unauthenticated HTTP request and validating access based on response behavior and content.

References:


Type of change

  • New or existing module/payload change

Checklist

  • I've run make pre-commit, it didn't generate any changes
  • I've run make test, all tests passed locally

Additional details

Tested against:

  • Local mock Triofox endpoint
  • Manual validation using curl
    Since the vulnerable version is not publicly available anymore , I could not test it against the actual server , rather I checked that the modules is correct in syntax and the detection logic is consistent with nuclie and huntress .

@coderabbitai

coderabbitai Bot commented Jan 22, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 105f78e3-958a-4f35-a633-bb10053e6aad

📥 Commits

Reviewing files that changed from the base of the PR and between ef245e0 and f3e159b.

📒 Files selected for processing (1)
  • docs/Modules.md
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/Modules.md

Summary by CodeRabbit

Release Notes

  • New Features

    • Added a new vulnerability detection for Gladinet Triofox improper access control (CVE-2025-12480) with severity rating 9.1.
  • Documentation

    • Updated the modules documentation to include the newly added Triofox vulnerability check.

Walkthrough

Adds a Triofox vulnerability module for CVE-2025-12480 and registers it in the module documentation. The module probes /management/admindatabase.aspx over HTTP(S) and validates status code and response content.

Changes

Triofox vulnerability module

Layer / File(s) Summary
Module registration and vulnerability probe
docs/Modules.md, nettacker/modules/vuln/triofox_improper_access_cve_2025_12480.yaml
Adds the Triofox module documentation entry and a YAML definition with CVE metadata, an HTTP GET probe, and response validation requiring status code 200 and matching content patterns.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Suggested labels: new module

Suggested reviewers: securestep9

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: adding a new Triofox CVE-2025-12480 vulnerability detection module.
Description check ✅ Passed The description is directly related to the changeset and explains the new Triofox vulnerability detection module and testing performed.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@nettacker/modules/vuln/triofox_improper_access_cve_2025_12480.yaml`:
- Around line 1-24: The severity field in the info block for
triofox_improper_access_control_cve_2025_12480_vuln is incorrect; change the
severity value from 9.8 to the official CVSS v3 base score 9.1 by editing the
severity key in the YAML (info.name:
triofox_improper_access_control_cve_2025_12480_vuln, field: severity).
🧹 Nitpick comments (2)
nettacker/modules/vuln/triofox_improper_access_cve_2025_12480.yaml (2)

34-34: Clarify the ssl: false setting.

Setting ssl: false disables SSL certificate verification. While this allows detecting vulnerable instances with self-signed certificates, it should be documented that this is intentional. This is a common pattern in vulnerability scanners but worth noting.


45-47: Consider adding common alternative ports.

Triofox may be deployed on non-standard ports like 8080 or 8443. This is consistent with other modules in the repository (e.g., joomla_cve_2023_23752, paloalto modules), and adding these ports would improve detection coverage.

♻️ Suggested enhancement
              ports:
                - 80
                - 443
+               - 8080
+               - 8443

Comment thread nettacker/modules/vuln/triofox_improper_access_cve_2025_12480.yaml
Signed-off-by: Aarush <cs24b064@smail.iitm.ac.in>

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@nettacker/modules/vuln/triofox_improper_access_cve_2025_12480.yaml`:
- Around line 1-4: The repository requires signed commits before merge; sign all
new and existing commits that touch the
triofox_improper_access_control_cve_2025_12480_vuln metadata (the YAML change
shown) by configuring a GPG or SSH signing key locally, committing future
changes with git commit -S, and re-signing past unsigned commits with an
interactive rebase (e.g., git rebase -i --exec "git commit --amend --no-edit -S"
<base>) then push the branch with --force-with-lease so CI pre-merge checks
accept the update.
🧹 Nitpick comments (1)
nettacker/modules/vuln/triofox_improper_access_cve_2025_12480.yaml (1)

6-9: Broaden content match for CentreStack or narrow scope.
Line 6–7 mentions CentreStack, but Line 57 only matches “Triofox Enterprise”. If CentreStack branding differs, the detector may miss affected instances. Consider adding an alternate token (e.g., CentreStack) or update the description to Triofox-only after validating actual responses.

Also applies to: 56-57

Comment thread nettacker/modules/vuln/triofox_improper_access_cve_2025_12480.yaml
@securestep9

Copy link
Copy Markdown
Collaborator

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f3e159b07e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/Modules.md
- '**teamcity_cve_2024_27198_vuln**' – check the target for TeamCity CVE-2024-27198 vulnerability
- '**tieline_cve_2021_35336_vuln**' – check the target for Tieline CVE-2021-35336 vulnerability
- '**tjws_cve_2021_37573_vuln**' – check the target for TJWS CVE-2021-37573 vulnerability
- '**triofox_improper_access_control_cve_2025_12480_vuln**' - Checks for an unauthenticated improper access control vulnerability in Gladinet Triofox

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Align the documented name with the loadable module name

Users who copy this name into -m/--modules cannot run the new scanner: module discovery derives the identifier from the filename as triofox_improper_access_cve_2025_12480_vuln, while this line documents an extra _control. The argument parser consequently reports that the documented scan module was not found; rename the file or use the filename-derived identifier consistently.

Useful? React with 👍 / 👎.

- unauth
- exposure
- triofox
- kev

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use the established cisa_kev profile tag

When users select --profile cisa_kev, this module is omitted because profile membership is built from exact tag strings and every other KEV module uses cisa_kev; this new kev tag instead creates a separate one-module profile. Since the module is intentionally marked as KEV, use the established tag so KEV-focused scans include this check.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants