dbcve.org
Attendance ManagerWordPress extension · Sukimalab

CVE-2019-5971

HIGH · 8.8 CVSS v3.0 Published 2019-07-05
Fix available
A fix is available. Upgrade to after 0.5.6 or later.
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 Attendance Manager 0.5.6 and earlier allows remote attackers to hijack the authentication of administrators via unspecified vectors.

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 confidence

Cross-site request forgery (CSRF) vulnerability in Attendance Manager 0.5.6 and earlier allows remote attackers to hijack the authentication of administrators. The flaw enables malicious requests to be forged on behalf of authenticated admin users without their knowledge, likely through crafted HTML or JavaScript embedded in third-party sites.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) for all state-changing admin operations, validate the Referer/Origin header on POST requests, and set SameSite attribute on session cookies to prevent cross-origin request submission.

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
Attendance ManagerWordPress extension
Affected:<= 0.5.6

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.0/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. Check installed version of Attendance Manager
    Locate the version information for Sukimalab Attendance Manager - typically found in the application metadata, version file, or about page. Compare your installed version against the affected range of <= 0.5.6.
    Affected if The installed version is 0.5.6 or earlier.
  2. Inspect admin forms for anti-CSRF tokens
    Log in as an administrator and navigate to pages with state-changing operations (such as user management, settings, or attendance modifications). View the HTML source of the forms and check whether each form includes a hidden input field containing a unique token value, or check if the application uses other anti-CSRF mechanisms.
    Affected if Admin forms lack anti-CSRF tokens or other CSRF protections.
  3. Inspect session cookie SameSite attribute
    Log into the application and open browser developer tools. Navigate to the Application or Cookies panel and examine the session cookie(s). Check whether the SameSite attribute is set to 'Strict' or 'Lax', or is missing entirely.
    Affected if The session cookie does not have SameSite attribute set, or it is set to 'None' without Secure flag.
  4. Test Referer/Origin header validation
    Submit an admin action via a crafted request from a third-party origin (or using a tool to modify the Referer/Origin headers). Observe whether the server accepts or rejects the request when these headers are missing or originate from an untrusted domain.
    Affected if The server accepts state-changing admin requests without validating Referer or Origin headers.

A user is affected if they run Sukimalab Attendance Manager version 0.5.6 or earlier AND the admin interface lacks anti-CSRF tokens in forms, session cookies lack SameSite attributes, and the server does not validate Referer/Origin headers on admin actions.

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 0.5.6
Interim mitigation

Implement anti-CSRF tokens (synchronizer token pattern) for all state-changing admin operations, validate the Referer/Origin header on POST requests, and set SameSite attribute on session cookies to prevent cross-origin request submission.

Fix this in Attendance Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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