dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-38873

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue was discovered in the friendlycaptcha_official (aka Integration of Friendly Captcha) extension before 0.1.4 for TYPO3. The extension fails to check the requirement of the captcha field in submitted form data, allowing a remote user to bypass the captcha check. This only affects the captcha integration for the ext:form extension.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Friendly Captcha TYPO3 extension before version 0.1.4 does not validate that the captcha field is present or properly completed in form submissions to the ext:form extension. This allows attackers to bypass the captcha protection entirely by simply omitting or manipulating the captcha field in submitted form data.

MitigationUpdate the friendlycaptcha_official extension to version 0.1.4 or later, which implements proper validation of the captcha field requirement in form submissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if friendlycaptcha_official extension is installed
    Run 'composer show friendsoftypo3/friendly-captcha' or check the extensions directory for friendlycaptcha_official
    Affected if The extension is present in the TYPO3 installation
  2. Determine installed version of friendlycaptcha_official
    Run 'composer show friendsoftypo3/friendly-captcha' and note the version number, or check ext_emconf.php for version
    Affected if Version is below 0.1.4 (e.g., 0.1.3, 0.1.2, etc.)
  3. Verify ext:form extension is active
    Run 'typo3cms extension:list' or check Composer dependencies for ext:form (typo3/cms-form)
    Affected if TYPO3 form extension is installed and active in the system
  4. Check form configurations using FriendlyCaptcha
    Inspect form definitions in Configuration/Yaml/ or database for forms with FriendlyCaptcha validator enabled
    Affected if Forms configured to use FriendlyCaptcha as a validator are present

You are affected if friendlycaptcha_official extension is installed with a version below 0.1.4 and forms using the FriendlyCaptcha validator exist in the environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the friendlycaptcha_official extension to version 0.1.4 or later, which implements proper validation of the captcha field requirement in form submissions.

Recommended fix High confidence

Upgrade to friendlycaptcha_official version 0.1.4 or later

  1. 1. Navigate to the TYPO3 Extension Manager (ADMIN TOOLS > Extensions)
  2. 2. Search for the 'friendlycaptcha_official' extension in the installed extensions list
  3. 3. Click on the extension to view its details
  4. 4. Check the currently installed version - ensure it is below 0.1.4
  5. 5. Click the 'Update' button next to the extension to install the latest version
  6. 6. Verify that version 0.1.4 or later is now installed
  7. 7. Clear the TYPO3 cache (if applicable) to ensure the updated extension is loaded properly
  8. 8. Test form submissions with the captcha to verify the vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-38873 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-38873 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data