CVE-2026-3781
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 · uneditedThe Attendance Manager plugin for WordPress is vulnerable to SQL Injection via the 'attmgr_off' parameter in all versions up to, and including, 0.6.2. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
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 confidenceThe Attendance Manager WordPress plugin (versions up to 0.6.2) contains a SQL injection vulnerability in the 'attmgr_off' parameter. The flaw results from insufficient input escaping and the absence of prepared statements in the SQL query, allowing authenticated attackers with Subscriber-level permissions or higher to inject arbitrary SQL commands and extract sensitive database information.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Attendance Manager plugin is installedIn 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 indicator in the main PHP file header.Affected if The plugin is installed and active
-
Check installed plugin versionOpen the main plugin file (attendance-manager.php or similar) and locate the Version header comment, or view the plugin details in WordPress admin plugins list.Affected if The version is 0.6.2 or lower (any version up to and including 0.6.2)
-
Confirm 'attmgr_off' parameter is accessibleSearch plugin source code for occurrences of 'attmgr_off' in PHP files. Check if this parameter is used in any SQL queries without prepared statements. Look in files that handle request parameters (GET/POST).Affected if The parameter 'attmgr_off' is found in SQL query code without proper sanitization or prepared statements
-
Verify minimum authentication requirement existsCheck if the WordPress site allows Subscriber-level user accounts, or review the plugin's capability checks around the vulnerable code to see if Subscriber role can access it.Affected if Subscriber-level or higher user accounts can exist on the site, and the vulnerable code is accessible to them
A site is affected if the Attendance Manager plugin version is 0.6.2 or lower, the 'attmgr_off' parameter is used in unsanitized SQL queries within the plugin, and authenticated users with Subscriber-level access can reach the vulnerable code path.
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 the Attendance Manager plugin to the latest version once available. If no patch exists, remediate by implementing proper parameterization with prepared statements for all SQL queries and ensuring adequate input sanitization on the attmgr_off parameter.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3781 — 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-3781 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