dbcve.org
CtparentalApplication · Ctparental Project

CVE-2021-37367

HIGH · 7.8 CVSS v3.1 Published 2021-08-10
Fix available
A fix is available. Upgrade to 4.45.07 or later.
See remediation →
80/100
Remediation priority · High
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
CTparental before 4.45.07 is affected by a code execution vulnerability in the CTparental admin panel. Because The file "bl_categories_help.php" is vulnerable to directory traversal, an attacker can create a file that contains scripts and run arbitrary commands.

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

CTparental before version 4.45.07 contains a directory traversal vulnerability in the admin panel file bl_categories_help.php. This flaw allows authenticated or potentially unauthenticated attackers to write arbitrary files to the filesystem and execute them, leading to remote code execution.

MitigationUpgrade CTparental to version 4.45.07 or later. If immediate patching is not possible, restrict access to the admin panel and implement strict input validation on file path parameters in bl_categories_help.php.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CtparentalApplication
Affected:< 4.45.07

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify CTparental installation exists
    Locate the CTparental installation directory on the server. Common paths may include /var/www/, /var/www/html/, or the web root. Look for the main CTparental files including bl_categories_help.php in the admin panel area.
    Affected if CTparental is not found in the expected installation directories
  2. Determine installed CTparental version
    Check the version information in CTparental's source files, typically found in a version file, changelog, or the main index/bootstrap file. Compare the version number against the vulnerable range: < 4.45.07
    Affected if The installed version is any version before 4.45.07 (e.g., 4.45.06, 4.44.x, etc.)
  3. Confirm vulnerable file exists
    Locate the file bl_categories_help.php within the admin panel directory structure of the CTparental installation.
    Affected if The file bl_categories_help.php exists in the admin panel directory
  4. Check admin panel accessibility
    Verify whether the CTparental admin panel is accessible via the web server. This may involve checking web server configuration, .htaccess restrictions, or direct HTTP access to the admin panel URL.
    Affected if The admin panel is accessible without proper access restrictions or authentication is weak/missing
  5. Inspect file operation parameters in bl_categories_help.php
    Examine the source code of bl_categories_help.php for file write operations that accept user-supplied path parameters without proper validation. Look for functions that handle file paths used in directory traversal patterns.
    Affected if The code contains file write operations that do not sanitize path parameters, allowing directory traversal characters (e.g., ../)

A user is affected if CTparental version is below 4.45.07, the vulnerable file bl_categories_help.php exists, and the admin panel or its file operations are accessible, allowing directory traversal for arbitrary file writes.

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
Upgrade available Upgrade to 4.45.07 or later
Fixed in 4.45.07
Interim mitigation

Upgrade CTparental to version 4.45.07 or later. If immediate patching is not possible, restrict access to the admin panel and implement strict input validation on file path parameters in bl_categories_help.php.

Recommended fix Moderate confidence

4.45.07 or later

  1. 1. Back up the current Ctparental installation and database before proceeding with any changes.
  2. 2. Update Ctparental to version 4.45.07 or later using your distribution's package manager or the project's official installation method.
  3. 3. Verify the update was successful by checking the installed version.
  4. 4. Confirm that the bl_categories_help.php file has been updated or removed as part of the patch.
  5. 5. Test the admin panel functionality to ensure the fix does not break legitimate features.

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

Fix this in Ctparental Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-37367 — 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-2021-37367 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