IdwebApplication · Idattend

CVE-2023-27375

HIGH · 7.5 CVSS v3.1 Published 2023-10-25
Fix available
A fix is available. Upgrade to after 3.1.052 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Missing authentication in the StudentPopupDetails_ContactDetails method in IDAttend’s IDWeb application 3.1.052 and earlier allows extraction of sensitive student data by unauthenticated attackers.

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

The IDAttend IDWeb application versions 3.1.052 and earlier contain a missing authentication vulnerability in the StudentPopupDetails_ContactDetails method. This endpoint exposes sensitive student contact information to unauthenticated attackers, allowing complete extraction of this data without any credentials or access rights.

MitigationImplement proper authentication and authorization checks on the StudentPopupDetails_ContactDetails method to ensure only authenticated and authorized users can access student contact details. Consider also implementing role-based access controls.

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
IdwebApplication
Affected:<= 3.1.052

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm IDAttend IDWeb installation
    Locate and identify the IDAttend IDWeb application in your environment - check web application directories, running services, or installed software listings
    Affected if IDAttend IDWeb is present in the environment
  2. Check installed version
    Retrieve the version number of the IDAttend IDWeb installation and compare it against the affected range (<= 3.1.052)
    Affected if Installed version is 3.1.052 or earlier
  3. Test endpoint accessibility
    Send an HTTP GET request to the StudentPopupDetails_ContactDetails endpoint without providing any authentication credentials
    Affected if The endpoint responds without requiring authentication
  4. Verify sensitive data exposure
    Examine the HTTP response from the unauthenticated request - check if student contact information such as names, phone numbers, addresses, or email addresses is returned
    Affected if The response contains student contact details without any authentication

You are affected if you have IDAttend IDWeb version 3.1.052 or earlier AND the StudentPopupDetails_ContactDetails endpoint is accessible and returns student contact information without authentication.

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
Upgrade available Upgrade to a release after 3.1.052
Interim mitigation

Implement proper authentication and authorization checks on the StudentPopupDetails_ContactDetails method to ensure only authenticated and authorized users can access student contact details. Consider also implementing role-based access controls.

Fix this in Idweb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-27375 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