Skip to content

fix: validate force exploit options per module - #13

Merged
setuidloot merged 1 commit into
mainfrom
fix/validate-forceexploit-module-options
Apr 25, 2026
Merged

setuidloot merged 1 commit into
mainfrom
fix/validate-forceexploit-module-options

Conversation

@setuidloot

Copy link
Copy Markdown
Owner

Summary

  • make run_exploit inject ForceExploit/AutoCheck only when the selected exploit module actually supports those options
  • avoid invalid-option failures on modules that do not expose those advanced toggles (for example multi/http/php_cgi_arg_injection)
  • extend force-exploit regression tests to model module option capabilities and add a direct unsupported-option coverage case

Closes #63

Test plan

  • source ../exploitmcp/.venv/bin/activate && python3 -m pytest tests/test_force_exploit_autocheck.py tests/test_timeout_cap.py -q

Made with Cursor

Only inject ForceExploit and AutoCheck in run_exploit when the selected module actually supports those options, preventing invalid-option failures on modules like php_cgi_arg_injection. Extend force-exploit tests with supported/unsupported option coverage and robust async mock assertions.

Made-with: Cursor
@setuidloot
setuidloot merged commit 9762598 into main Apr 25, 2026
1 check passed
setuidloot pushed a commit that referenced this pull request Apr 29, 2026
…options

fix: validate force exploit options per module
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.

1 participant