Skip to content
KitploitKITPLOIT
ツールエクスプロイトブログ
Log in
提出
ツールエクスプロイトブログ
提出

ハッキング、侵入テスト、サイバーセキュリティツールをあなたのセキュリティアーセナルに!

Kitploitはハッキング、サイバーセキュリティ、ペネトレーションテストのツールディレクトリです。最新のプロジェクトアップデートを見つけて、脆弱性の発見、システム分析、テストの自動化、セキュリティの強化を行いましょう。

フィードお問い合わせプライバシー© 2026 Kitploit

ツールディレクトリ

カテゴリ

すべてのカテゴリを見る
Loading categories
CVE-2026-84753 — Proof-of-concept exploit and lab for CVE-2026-84753, an unauthenticated PHP Object Injection in Mail Mint <= 1.31.0 via the mint-form-submit REST endpoint. | Kitploit
ツール/GitHubGitHub/abraxas/cve-2026-84753
Vulnerability AnalysisExploitationWeb Application ExploitationWeb SecurityPenetration TestingLabs & Practice
GitHubabraxas/cve-2026-84753

CVE-2026-84753

Proof-of-concept exploit and lab for CVE-2026-84753, an unauthenticated PHP Object Injection in Mail Mint <= 1.31.0 via the mint-form-submit REST endpoint.

リポジトリを見る
1182日前未レビュー

人気

すべて見る →

コミュニティで最も使われているツールを見つけましょう。

すべてのツールを探索

ツールコレクションを閲覧

すべてのツールを見る →
共有
要求された言語のコンテンツは利用できません。英語版を表示しています。

Abraxas Labs - CVE-2026-84753

abraxaslabs.tech  ·  github.com/abraxas  ·  @abraxas_null  ·  [email protected]  ·  CVE-2026-84753

CVE-2026-84753

Mail Mint 1.31.0 - WPFunnels

I am @abraxas_null. Loopback lab. The client is CVE-2026-84753-Abraxas-Labs.py.

The function is named safe. Unauthenticated REST mint-form-submit copies extra fields into contact meta, then ContactModel::safe_unserialize_meta() maybe_unserializes them. Objects instantiate before the is_array discard. The JSON can still say the form is not valid. The class still ran. Patched in 1.31.1 (is_serialized reject, allowed_classes => false).

CVECVE-2026-84753 · CVE.org
CWECWE-502
CVSSCritical: 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
ProductMail Mint
Affectedall versions through 1.31.0 (inclusive)
Patched1.31.1 and later
Authnone
LicenseGNU Affero GPL v3.0
Lab127.0.0.1 only

What an attacker can do

POST the public form twice with the same email and a serialized object in an extra field. First request stores. Second request loads. __wakeup / __destruct run in the WordPress process. A POP gadget on a real autoload is RCE. The lab ships a canary class, not a gadget.


How I found it

Patchstack named object injection. I read FormAction::handle_form_submission, then safe_unserialize_meta. HTTP is REST, not an ajax action= of that name.

Harvest MM_NONCE= from the public page the way a visitor would. Two POSTs, same email, extra field is a serialized instance of the lab canary. Witness is POCWitness84753 in the body or debug.log.

Wrong turns: treating action=safe_unserialize_meta as a route; stopping at {"status":"success","message":"Form is not valid"} (that JSON is not a miss); hard-coding a nonce; calling this "WordPress unserializes meta" (core post meta is a different story).


The lab

Port 8088. Mail Mint 1.31.0. Seed form id 1 and page slug mm-lab-nonce.

  • lab/Dockerfile
  • lab/docker-compose.override.yml
  • lab/docker-compose.yml

Target only 127.0.0.1:8088 (or the loopback you bound).

cd lab
docker compose up --force-recreate
python3 ../CVE-2026-84753-Abraxas-Labs.py

Witness: POCWitness84753 from __wakeup / __destruct in the second POST body or debug.log. Form-invalid JSON without that string is not it.

Ways to lose without learning anything:

  • form message JSON without the class name
  • hard-coded nonce / missing wp_rest nonce
  • reverse shell or a POP gadget in the pack

The fix

Update Mail Mint to 1.31.1 or newer. Re-run CVE-2026-84753-Abraxas-Labs.py against the patched build: POCWitness84753 must not appear.


References

  • CVE-2026-84753 · NVD

  • CVE-2026-84753 · CVE.org

  • patchstack.com/database/wordpress/plugin/mail-mint/vulnerability/wordpress-mail-mint-plugin-1-31-0-php-object-injection-vulnerability?_s_id=cve

  • github.com/advisories/GHSA-28vg-wv39-3g8h

  • nvd.nist.gov/vuln/detail/CVE-2026-84753

  • Plugin directory: mail-mint

  • Trac browser: plugins.trac.wordpress.org/mail-mint

  • SVN tags: plugins.svn.wordpress.org/mail-mint

  • Abraxas Labs: abraxaslabs.tech · github.com/abraxas · @abraxas_null


License

GNU Affero GPL v3.0. See LICENSE.


The client talks to loopback. Using it against systems you do not own is not authorized by Abraxas Labs. No warranty.

abraxaslabs.tech · github.com/abraxas · @abraxas_null

ツールをダウンロード