CVE-2023-30487
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in ThimPress LearnPress Export Import plugin <= 4.0.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 · high confidenceUnauthenticated reflected cross-site scripting (XSS) vulnerability in the ThimPress LearnPress Export Import plugin allows attackers to inject malicious scripts via unsanitized input parameters, which are then reflected back to the victim in the HTTP response.
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<= 4.0.2CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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.
-
Identify LearnPress Export Import plugin installationLocate the LearnPress Export Import plugin in your WordPress installation (typically in wp-content/plugins/ directory) and check the version number from the plugin's main PHP file or readme.txtAffected if Plugin version is 4.0.2 or lower, or version cannot be determined (indicating outdated installation)
-
Confirm plugin is activeCheck WordPress admin panel under Plugins > Installed Plugins, or query the wp_options table for active_plugins setting to verify LearnPress Export Import is enabledAffected if Plugin is installed and activated on the WordPress site
-
Verify WordPress version of LearnPress coreCheck the main LearnPress plugin version (distinct from Export Import addon) at Plugins > Installed Plugins or in wp-content/plugins/learnpress/ directoryAffected if LearnPress core is present; the Export Import addon is bundled with or depends on LearnPress <= 4.0.2
-
Test for reflected XSS in export/import parametersUsing a browser or HTTP tool, access common LearnPress Export Import endpoints (such as /wp-admin/admin-ajax.php with action=lp_export or similar import/export actions) and inject a test XSS payload in URL parameters to observe if the input is reflected unsanitized in the responseAffected if Input submitted via export/import parameters is returned in the HTTP response without proper encoding or sanitization
-
Review HTTP response headers and bodySubmit requests to LearnPress Export Import functionality with various parameter values and examine if those values appear verbatim (unencoded) in the page outputAffected if Any parameter value from the request is reflected directly in the response without HTML entity encoding
The environment is affected if LearnPress Export Import plugin version 4.0.2 or lower is installed and active, with the export/import feature accessible to unauthenticated users and reflecting input without sanitization.
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 LearnPress Export Import plugin to version higher than 4.0.2; apply web application firewall rules to block XSS attack patterns as temporary measure until patch is applied.
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30487 — 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-30487 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