dbcve.org
IcmsApplication · Icmsdev

CVE-2023-42321

HIGH · 8.8 CVSS v3.1 Published 2023-09-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross Site Request Forgery (CSRF) vulnerability in icmsdev iCMSv.7.0.16 allows a remote attacker to execute arbitrary code via the user.admincp.php, members.admincp.php, and group.admincp.php files.

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

CSRF vulnerability in iCMSv.7.0.16 admin panel files (user.admincp.php, members.admincp.php, group.admincp.php) allows remote attackers to trick authenticated administrators into executing unintended actions that can lead to arbitrary code execution on the server.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing admin forms and validate request origin via SameSite cookies or Referer/Origin header checks.

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
IcmsApplication
Affected:= 7.0.16

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify iCMS version
    Locate the version file or check the admin dashboard footer for the iCMS version number. Common locations include version.php, about.php, or the login/admin footer.
    Affected if The installed version is exactly 7.0.16
  2. Verify admin panel accessibility
    Confirm the admin panel files (user.admincp.php, members.admincp.php, group.admincp.php) exist in the web root under the admincp directory.
    Affected if The affected PHP files are present and accessible on the server
  3. Inspect user.admincp.php for CSRF protection
    Open user.admincp.php in a text editor or via command line and search for anti-CSRF token implementation: look for tokens, form tokens, csrf, or synchronizer token patterns. Check if state-changing forms (add/edit/delete user) include hidden token fields.
    Affected if No anti-CSRF token fields are found in forms that modify user data, or tokens are not validated on submission
  4. Inspect members.admincp.php for CSRF protection
    Open members.admincp.php and examine forms that perform member operations (add/edit/delete members, profile updates). Look for hidden token fields and server-side token validation.
    Affected if Member modification forms lack CSRF token fields or do not validate tokens server-side
  5. Inspect group.admincp.php for CSRF protection
    Open group.admincp.php and examine group management forms (create/edit/delete user groups, permission changes). Search for token implementation and validation logic.
    Affected if Group management forms do not include or validate anti-CSRF tokens
  6. Check cookie security settings
    Examine the application configuration or PHP session settings for SameSite cookie attributes. Look in config files or session initialization code for SameSite=Strict or SameSite=Lax settings.
    Affected if Cookies are missing SameSite attributes and Referer/Origin header validation is not performed on admin actions

A user is affected if running iCMS version 7.0.16 and the admin panel files lack anti-CSRF token protection on state-changing forms, allowing attackers to forge authenticated admin requests.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (synchronizer token pattern) on all state-changing admin forms and validate request origin via SameSite cookies or Referer/Origin header checks.

Fix this in Icms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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