CVE-2023-23076
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 · uneditedOS Command injection vulnerability in Support Center Plus 11 via Executor in Action when creating new schedules.
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 confidenceOS Command injection vulnerability in Support Center Plus 11 (version 11) in the Executor component within the Action functionality when creating new schedules. An authenticated attacker can inject arbitrary OS commands through unsanitized input parameters in the scheduling feature.
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= 11.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Support Center Plus is installedCheck for Support Center Plus installation by looking for the application in your programs list, or locate the installation directory (typically under ManageEngine\SupportCenter Plus in Program Files).Affected if Support Center Plus is not installed on the system.
-
Check installed version numberAccess the admin console of Support Center Plus and navigate to the About section (usually under Admin > About or Help > About) to view the exact version, or check the version.txt or version.info file in the installation directory.Affected if The installed version is exactly 11.0 (11.0.0).
-
Confirm scheduling feature is accessibleLog into Support Center Plus as an authenticated user and navigate to the Action or Scheduling functionality (typically under Actions > Schedule Task or similar path in the admin or user interface).Affected if The scheduling/Action feature is exposed and accessible to authenticated users.
-
Verify Executor component configurationCheck the Support Center Plus configuration files (typically in the conf directory within the installation folder) for the Executor component settings related to scheduled actions.Affected if Executor component for Action scheduling is enabled in the configuration.
-
Review user access to scheduling featureCheck user roles and permissions in the admin console to see which authenticated users have access to creating or modifying schedules through the Action functionality.Affected if Authenticated users (other than administrators) have permissions to access the scheduling/Action functionality.
You are affected if Support Center Plus version 11.0 is installed and the scheduling/Action feature with the Executor component is accessible to authenticated users in your environment.
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 dataApply vendor security patches for Support Center Plus 11. If no patch available, temporarily restrict access to the scheduling/Action functionality to trusted administrators only and implement input validation at the application layer to sanitize special characters in schedule parameters.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23076 — 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-23076 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