Wp AbstractsWordPress extension · Kevonadonis
CVE-2023-29385
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 Kevon Adonis WP Abstracts plugin <= 2.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 · high confidenceA reflected cross-site scripting (XSS) vulnerability exists in the Kevon Adonis WP Abstracts plugin versions 2.6.2 and below. The vulnerability is unauthenticated, meaning attackers do not need valid credentials to exploit it. Attackers can craft malicious URLs containing JavaScript payloads that get executed in the victim's browser when they interact with the affected page.
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
Wp AbstractsWordPress extension
<= 2.6.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.
-
Locate the WP Abstracts plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find 'WP Abstracts' by Kevonadonis, and note the version number displayed below the plugin nameAffected if Version is 2.6.2 or lower (including no version displayed indicating outdated installation)
-
Confirm plugin is activeCheck the Plugins page in WordPress admin - the WP Abstracts plugin shows as 'Active' under its statusAffected if Plugin is currently active (the XSS is exploitable regardless of user authentication status)
-
Identify exposed endpointsReview site for pages using WP Abstracts functionality - common paths include '/wp abstracts/', '/abstracts/', or query parameters handling abstract submissionsAffected if The plugin handles user-supplied input via URL parameters without sanitization (this is the root XSS condition)
-
Test for reflected parameter handlingIf you have access to the site, inspect page source for any URL parameters (such as 'abstract_id', 'action', or 'page' parameters) that might be reflected unescaped in HTML outputAffected if URL parameters are reflected directly into HTML without output encoding (indicating the vulnerable code pattern)
-
Compare against CVE scopeCross-reference your findings: plugin version <= 2.6.2 AND active AND handles URL parameters on the frontendAffected if All three conditions true - the installed version falls within the affected range and the plugin is operational
Your environment is affected if the WP Abstracts plugin is active and the installed version is 2.6.2 or lower, since the reflected XSS vulnerability exists in all versions up to and including 2.6.2.
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 WP Abstracts plugin to the latest version (above 2.6.2) which contains the security patch. If an update is unavailable, consider disabling the plugin until a patched version is released.
Fix this in Wp Abstracts
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29385 — 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-29385 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