freeCap CAPTCHA extension for TYPO3 has vulnerability in the session handling feature
CVE-2009-3818GHSA-m8c5-5g3h-jjfg
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (sjbr/sr-freecap 1.2.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist sjbr/sr-freecap
- Affected
- < 1.2.2
- Fixed in
- 1.2.2
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-m8c5-5g3h-jjfg lists affected ranges: Packagist sjbr/sr-freecap >=0 <1.2.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- CVE-2009-3818: 1.24% estimated exploitation activity in the next 30 days; percentile 69.17 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Unspecified vulnerability in the session handling feature in freeCap CAPTCHA (srfreecap) extension 1.2.0 and earlier for TYPO3 has unknown impact and attack vectors.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-m8c5-5g3h-jjfg
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2009-3818 Advisory: freeCap CAPTCHA extension for TYPO3 has vulnerability in the session handling feature IDs: CVE-2009-3818, GHSA-m8c5-5g3h-jjfg Record: https://patchnext.com/advisories/cve-2009-3818 (revision 1, source checked 26 Oct 2026, 14:30 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: sjbr/sr-freecap 1.2.2. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist sjbr/sr-freecap: affected < 1.2.2; fixed in 1.2.2 ## Suggested inspection (read-only) - Packagist sjbr/sr-freecap: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on sjbr/sr-freecap. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-m8c5-5g3h-jjfg (GitHub-reviewed advisory GHSA-m8c5-5g3h-jjfg lists affected ranges: Packagist sjbr/sr-freecap >=0 <1.2.2) Commands are suggestions: review each one before running it.
Loading voting…