CVE-2025-58635
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 DevItems Support Genix support-genix-lite allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Support Genix: from n/a through <= 1.4.23.
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 confidenceA missing authorization vulnerability in Support Genix (version <= 1.4.23) allows attackers to exploit incorrectly configured access control security levels. The application fails to properly validate authorization permissions before allowing access to certain functionality, potentially enabling unauthorized users to perform actions outside their intended privilege level.
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 installed Support Genix versionLocate the version file or About page in the Support Genix installation (commonly in config files, composer.json, or admin dashboard About section)Affected if The installed version is 1.4.23 or lower
-
Review access control security level configurationExamine the application's access control settings, typically found in security configuration files, admin panel permissions settings, or role-based access control (RBAC) definitionsAffected if Security levels are set to low, misconfigured, or use default settings that allow privilege escalation
-
Test sensitive endpoint access with low-privilege accountCreate or use a low-privilege test account and attempt to access administrative functions, sensitive data endpoints, or functionality that should require higher privilegesAffected if Low-privilege users can access or execute actions intended for higher-privilege roles
-
Audit role permission mappingsReview the role-to-permission mapping configuration in the application database or config files, checking if all sensitive operations have proper role enforcementAffected if Certain functions or endpoints are not assigned to specific roles or have no permission checks defined
-
Inspect API endpoints for authorization enforcementReview API request handlers and controller code for proper authorization decorators or permission validation checks before executing sensitive operationsAffected if API endpoints lack authorization validation code or have empty permission checks
The environment is affected if Support Genix version is 1.4.23 or lower AND sensitive endpoints lack proper authorization enforcement or access control security levels are misconfigured.
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 on all sensitive endpoints and functions, ensuring that access control security levels are correctly configured and enforced for all user roles.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58635 — 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-2025-58635 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