CVE
ALTCHA Lib PHP captcha bypass via missing HMAC check in verifySolution
Affects altcha-org/altcha-lib-php 2.0.0 up to 2.0.3 when hmacSignatureSecret is set and the challenge payload omits the signature field. Fixed in 2.0.3.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.0.3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.0.3.
Summary
The ALTCHA PHP library (altcha-lib-php, from altcha-org) skips HMAC signature checks in its verifySolution method when a challenge has no signature field, even if a signature secret is configured. Remotely, without logging in, an attacker can remove the signature, choose easy challenge settings, solve the proof of work, and have the payload accepted, which bypasses the CAPTCHA control.
Original description
ALTCHA PHP is a lightweight PHP library for creating and verifying ALTCHA challenges. From 2.0.0 until 2.0.3, the verifySolution method skips HMAC signature verification when a challenge payload omits the signature field, even when hmacSignatureSecret is configured. An attacker can remove the signature, supply attacker-selected low-difficulty challenge parameters, solve the resulting proof of work, and submit a payload that verifies successfully, bypassing the CAPTCHA control. This issue is fixed in version 2.0.3.
Who should check
Teams running the altcha-org/altcha PHP library v2 (Composer) that set hmacSignatureSecret to protect ALTCHA CAPTCHA challenges.
“In altcha-org/altcha v2, the verifySolution method skips HMAC signature verification”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.0.3.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-71481 (ALTCHA PHP: verifySolution bypasses HMAC signature check when challenge signature is absent), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-71481 (entry last updated 2026-11-18):
Affected:
- altcha-org altcha-lib-php: from 2.0.0, fixed in 2.0.3
Fixed versions: 2.0.3.
Conditions (all must be true for the bug to be hit):
- The application sets hmacSignatureSecret on the altcha-org/altcha v2 PHP library. (source: https://github.com/altcha-org/altcha-lib-php/security/advisories/GHSA-82w8-65qw-gch6)
- The challenge payload omits the signature field. (source: https://github.com/altcha-org/altcha-lib-php/security/advisories/GHSA-82w8-65qw-gch6)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-71481 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-71481 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/altcha-org/altcha-lib-php/security/advisories/GHSA-82w8-65qw-gch6
- https://github.com/altcha-org/altcha-lib-php/commit/8b02ad2c9b82998613bac4d093517d457061cbbe
- https://github.com/altcha-org/altcha-lib-php/releases/tag/v2.0.3
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-71481
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-71481"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- altcha-org altcha-lib-php
From 2.0.0 · fixed in 2.0.3
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · altcha-org/altcha-lib-php · Advisory GHSA-82w8-65qw-gch6 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-71481 |
| Record | NVD · CVE-2026-71481 |
| Other links 2 | |
| Repository | GitHub · altcha-org/altcha-lib-php · Commit 8b02ad2c |
| Repository | GitHub · altcha-org/altcha-lib-php · Release v2.0.3 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-71481
Is CVE-2026-71481 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
verifySolution skips the HMAC signature check when the challenge payload has no signature field, even when hmacSignatureSecret is configured. An attacker can then create their own low-difficulty challenge, solve it, and get a payload that verifies as true, which bypasses the CAPTCHA entirely.Source: github.com
Which versions are affected by CVE-2026-71481?
altcha-lib-php: from 2.0.0 before 2.0.3.Source: cve.now feed data
Am I affected, and how do I check?
The affected range is altcha-org/altcha-lib-php from 2.0.0 up to but not including 2.0.3. Check the installed version with composer show altcha-org/altcha-lib-php or in composer.lock, and check whether hmacSignatureSecret is set in the application's ALTCHA configuration.Source: github.com
How do I fix CVE-2026-71481?
Upgrade altcha-org/altcha-lib-php to 2.0.3 or later, which is the fixed version in the affected range. No vendor patch identifiers are given in the checked facts.Source: github.com