CVE-2023-29173
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 · uneditedMissing Authorization vulnerability in AWESOME TOGI Product Category Tree allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Product Category Tree: from n/a through 2.5.
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 · moderate confidenceMissing authorization vulnerability in AWESOME TOGI Product Category Tree (versions through 2.5) allows unauthorized access due to incorrectly configured access control security levels. The Product Category Tree component fails to properly validate user permissions before granting access to sensitive category management functionality.
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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 if Product Category Tree component is installedSearch your system for the AWESOME TOGI Product Category Tree component or module. Check application directories, plugin listings, or component manifests for references to 'Product Category Tree' or 'AWESOME TOGI'.Affected if The component is present on the system and no additional authorization controls are enforced at a higher application layer.
-
Determine installed version of Product Category TreeLocate the version information for the Product Category Tree component in your installation. Check version files, about pages, or component metadata where the version number is recorded.Affected if The installed version is 2.5 or any earlier version (versions through 2.5 are affected per the CVE).
-
Verify access control security level configurationExamine the access control or security level settings specifically assigned to the Product Category Tree functionality. Look for security configuration files, role-based access settings, or permission matrices that define who can access category management features.Affected if The security level is set to a permissive or misconfigured state that allows unauthorized users to access sensitive category management functions.
-
Test for unauthorized access to category managementAttempt to access the Product Category Tree category management functionality using an account that should NOT have elevated privileges or administrative access to this component. Observe whether the system grants access without proper authorization validation.Affected if The system allows access to category management features without verifying user permissions, indicating the authorization check is not being enforced.
A user is affected if the Product Category Tree component (version 2.5 or earlier) is installed AND the access control security levels are misconfigured to allow unauthorized access to category management functionality.
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 dataImplement proper authorization checks at all entry points to the Product Category Tree functionality and ensure access control security levels are correctly configured according to the principle of least privilege.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29173 — 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-2023-29173 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