CVE-2026-52712
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 · uneditedSubscriber SQL Injection in Attendance Manager <= 0.6.2 versions.
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 confidenceSQL injection vulnerability in the Attendance Manager WordPress plugin versions 0.6.2 and below allows authenticated users with Subscriber-level privileges to inject malicious SQL statements via unsanitized input parameters.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:L
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 Attendance Manager plugin installationIn WordPress admin, go to Plugins > Installed Plugins and look for 'Attendance Manager', or check the plugin files in wp-content/plugins/attendance-manager/ for a version file or readme.txt containing the version numberAffected if Plugin is installed and version is 0.6.2 or below
-
Confirm plugin version numberOpen the plugin's main PHP file or readme.txt and locate the version declaration (e.g., 'Version: 0.6.2' or similar)Affected if Version listed is 0.6.2 or any version number lower than 0.6.2
-
Identify subscriber-level usersIn WordPress admin, go to Users > All Users and check the 'Role' column for any users assigned the 'Subscriber' role, or use WP-CLI: wp user list --role=subscriberAffected if At least one user with Subscriber role exists in the system
-
Verify vulnerable endpoint is accessibleCheck if the Attendance Manager plugin exposes any frontend or adminajax endpoints that accept user input (common parameters include user_id, date, status, or record IDs). Inspect plugin source code for PHP files handling database queries with direct $_GET, $_POST, or $_REQUEST variables without prepare() or sanitizationAffected if Plugin processes database queries using unsanitized input from authenticated users
-
Confirm SQL injection point existsReview plugin PHP files for SQL queries that concatenate user input directly into queries (look for '$wpdb->query', '$wpdb->get_results', or similar without $wpdb->prepare() wrapper)Affected if SQL queries use raw user input without parameterization
Your environment is affected if the Attendance Manager plugin version is 0.6.2 or below AND any subscriber-level user account exists, because the plugin allows SQL injection via unsanitized parameters accessible to authenticated subscribers.
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 dataUpdate Attendance Manager plugin to a version greater than 0.6.2 when available, or remove the plugin until a patch is released. Apply principle of least privilege to limit Subscriber role capabilities.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-52712 — 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-2026-52712 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