IdwebApplication · Idattend

CVE-2023-27258

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 GetStudentGroupStudents method in IDAttend’s IDWeb application 3.1.052 and earlier allows retrieval of student and teacher 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

Missing authentication in the GetStudentGroupStudents method in IDAttend's IDWeb application version 3.1.052 and earlier allows unauthenticated attackers to directly invoke this API method and retrieve sensitive student and teacher data without any credentials.

MitigationImplement authentication and authorization checks on the GetStudentGroupStudents endpoint and similar data retrieval methods; upgrade to a patched version if available; apply network segmentation to restrict access to the IDWeb application.

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. Identify IDAttend IDWeb installation
    Check for IDAttend IDWeb application files on the system, typically installed in web server directories (IIS/www root). Look for Idweb or IDAttend related directories and DLL files.
    Affected if IDAttend IDWeb application is present on the system
  2. Determine IDWeb version
    Locate version information in application files, assembly info, or configuration files. Check the bin directory for DLL version metadata, or look for version.txt/readme files in the application root.
    Affected if Version is 3.1.052 or earlier
  3. Verify GetStudentGroupStudents endpoint exposure
    Attempt to access the GetStudentGroupStudents API endpoint directly via HTTP request (e.g., GET/POST to the application's API URL) without providing any authentication tokens or credentials.
    Affected if The endpoint responds successfully and returns data without requiring authentication
  4. Check API authentication configuration
    Inspect the application's web.config or API configuration files for authentication settings on the GetStudentGroupStudents method. Look for [AllowAnonymous] attributes or missing [Authorize] decorators in the API controller.
    Affected if No authorization attributes are configured for the endpoint, or anonymous access is explicitly allowed

If IDAttend IDWeb version 3.1.052 or earlier is installed AND the GetStudentGroupStudents endpoint is accessible without authentication credentials, the environment is affected by this CVE.

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 authentication and authorization checks on the GetStudentGroupStudents endpoint and similar data retrieval methods; upgrade to a patched version if available; apply network segmentation to restrict access to the IDWeb application.

Fix this in Idweb Scoped from the published advisory
  • Consultation6.0 h
  • Implementation10.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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