CVE-2023-47823
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 · uneditedMissing Authorization vulnerability in nCrafts FormCraft allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects FormCraft: from n/a through 1.2.7.
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 confidenceFormCraft plugin versions through 1.2.7 contain a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. The application fails to properly verify user authorization before granting access to certain functionality or resources, potentially allowing unauthorized users to perform actions or access data they should not be permitted to reach.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Identify FormCraft plugin versionLocate the plugin file that contains the version information, commonly in the main plugin PHP file, readme.txt, or a version constant. Common paths include wp-content/plugins/formcraft/formcraft.php or similar. Look for a 'Version:' header or version variable.Affected if The installed version is 1.2.7 or any earlier version (1.2.6, 1.2.5, etc.)
-
Verify WordPress admin access controls existInspect the FormCraft plugin PHP files for functions that handle admin actions (form submissions, settings changes, export functions). Check if these functions include current_user_can(), is_user_logged_in(), or similar authorization checks before executing sensitive operations.Affected if Sensitive functions lack proper authorization checks and can be accessed without verifying user permissions
-
Test form submission endpointsSend a crafted request to form submission endpoints (typically at /?formcraft_new_form=1 or similar URLs used by FormCraft) while unauthenticated or as a low-privilege user. Observe if the request is processed without returning an authorization error.Affected if Form submission or data collection endpoints process requests from unauthorized users
-
Inspect access control configurationCheck the FormCraft settings panel in WordPress admin for any security level or access permission settings. Look for configuration options that control who can access forms, view submissions, or modify settings.Affected if Security level settings are misconfigured to allow public or low-privilege access to sensitive functionality
A user is affected if they have FormCraft plugin version 1.2.7 or lower installed AND sensitive plugin functions lack proper authorization checks or are accessible to unauthorized users.
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 dataImplement proper authorization checks throughout the application, ensuring all sensitive operations and resources verify the current user's permissions before allowing access. Upgrade to the latest version if available and conduct a security audit of access control logic.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2023-47823 — 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-2023-47823 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