CVE-2026-71481: ALTCHA PHP: verifySolution bypasses HMAC signature check when challenge signature is absent
High CVSS 7.5
- OSV id
- GHSA-82w8-65qw-gch6
- Also known as
- CVE-2026-71481
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| altcha-org/altcha Packagist |
>= 2.0.0, < 2.0.3 | 2.0.3 |
How to fix it
Upgrade altcha-org/altcha to 2.0.3 or later.
composer update altcha-org/altcha
# if composer.json blocks it: composer require "altcha-org/altcha:^2.0.3"
- If it is an indirect dependency, `composer update` the package that requires it, with dependencies.
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
Not sure whether your project uses an affected version? Check your lockfile below for free.
Details
In altcha-org/altcha v2, the verifySolution method skips HMAC signature verification when the signature field is absent from the challenge payload, even when hmacSignatureSecret is configured.
An attacker who strips the signature key from the challenge JSON passes the condition as false, bypassing tamper-detection entirely. The PoW solution check then runs against unverified parameters — allowing an attacker to self-issue a low-difficulty challenge, solve it trivially, and submit a payload that verifies as true.
Impact: Complete CAPTCHA bypass on any deployment that sets hmacSignatureSecret (the recommended production configuration).
Fix: The check was split so that a missing signature is explicitly rejected when a secret is configured.
References
- GHSA-82w8-65qw-gch6 on OSV.dev
- Web: https://github.com/altcha-org/altcha-lib-php/security/advisories/GHSA-82w8-65qw-gch6
- Web: https://github.com/altcha-org/altcha-lib-php/commit/8b02ad2c9b82998613bac4d093517d457061cbbe
- Package: https://github.com/altcha-org/altcha-lib-php
- Web: https://github.com/altcha-org/altcha-lib-php/releases/tag/v2.0.3
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.