Access Demo ImporterWordPress extension · Accesspressthemes
CVE-2022-23976
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 · uneditedCross-Site Request Forgery (CSRF) in Access Demo Importer <= 1.0.7 on WordPress allows an attacker to reset all data (posts / pages / media).
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Access Demo Importer WordPress plugin versions 1.0.7 and below allows unauthenticated attackers to trick authenticated administrators into resetting all site content (posts, pages, media) via maliciously crafted requests.
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
Access Demo ImporterWordPress extension
<= 1.0.7CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Access Demo Importer plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate 'Accesspressthemes Access Demo Importer' to see the version number. Alternatively, inspect the main plugin file at wp-content/plugins/access-demo-importer/ and look for the 'Version' header in the plugin comment block, or run `wp plugin list --status=active --fields=name,version` if WP-CLI is available.Affected if Version displayed is 1.0.7 or lower (e.g., 1.0.6, 1.0.5, 1.0.4, etc.)
-
Verify plugin is activeConfirm the Access Demo Importer plugin is currently activated in the WordPress site. In WP Admin, check Plugins > Installed Plugins to see if the plugin shows 'Activate' (inactive) or 'Deactivate' (active) link, or query the database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins'.Affected if Plugin is activated and appears in the active_plugins list
-
Confirm demo importer functionality existsCheck if the plugin's demo importer functions are accessible. Look for the demo importer admin menu item (usually under Appearance or a dedicated AccessPress menu), or inspect plugin files for the reset/import functions that handle data restoration. The vulnerable endpoint typically processes requests to reset site content.Affected if The demo importer panel or related reset functionality is present and accessible to an authenticated administrator
The environment is affected if Access Demo Importer version 1.0.7 or lower is installed and the plugin is active, allowing the CSRF vulnerability to be exploited against authenticated administrators.
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 Access Demo Importer to the latest version which implements proper anti-CSRF nonce validation on data reset functions; alternatively, disable the plugin until patched.
Fix this in Access Demo Importer
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23976 — 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-2022-23976 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