CVE-2021-37365
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 · uneditedCTparental before 4.45.03 is vulnerable to cross-site scripting (XSS) in the CTparental admin panel. In bl_categires_help.php, the 'categories' variable is assigned with the content of the query string param 'cat' without sanitization or encoding, enabling an attacker to inject malicious code into the output webpage.
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 confidenceCTparental before 4.45.03 contains a reflected XSS vulnerability in bl_categires_help.php where the 'cat' query parameter is assigned to the 'categories' variable without any input sanitization or output encoding, allowing injection of arbitrary JavaScript into the admin panel page.
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< 4.45.03CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Ctparental installation and versionLocate the Ctparental installation directory and find the version information, typically in a version file, changelog, or the main script header.Affected if The installed version is below 4.45.03 (e.g., 4.45.02, 4.45.01, etc.)
-
Locate vulnerable file bl_categires_help.phpSearch the Ctparental installation directory for the file bl_categires_help.php.Affected if The file exists in the installation, indicating the vulnerable component is present.
-
Inspect code handling of 'cat' parameterOpen bl_categires_help.php and examine how the 'cat' query parameter is handled. Look for assignment of the 'cat' parameter to a 'categories' variable without htmlspecialchars() or equivalent sanitization.Affected if The code shows direct assignment of $_GET['cat'] to a variable without sanitization (e.g., $categories = $_GET['cat']; without encoding)
-
Verify admin panel accessibilityConfirm the admin panel interface is accessible and the vulnerable page can be reached via URL.Affected if The admin panel is accessible and the bl_categires_help.php page can be loaded with a crafted 'cat' parameter
You are affected if Ctparental version is below 4.45.03 AND the bl_categires_help.php file exists with unsanitized 'cat' parameter handling AND the admin panel is accessible.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data4.45.03
Implement proper output encoding using htmlspecialchars() or equivalent when rendering the 'categories' variable, and validate the 'cat' parameter input against an allowlist of permitted values.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37365 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-37365 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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