CVE-2024-38744
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 Upqode Plum: Spin Wheel & Email Pop-up allows Accessing Functionality Not Properly Constrained by ACLs, Stored XSS.This issue affects Plum: Spin Wheel & Email Pop-up: from n/a through 2.0.
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 confidenceUpqode Plum: Spin Wheel & Email Pop-up plugin for WordPress contains both a Missing Authorization vulnerability allowing functionality access beyond proper ACL constraints and a Stored XSS vulnerability. An attacker with low-privilege access (or unauthenticated) could potentially exploit the authorization flaw to access admin-level functionality and inject malicious scripts that persist and execute for other users.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
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 Upqode Plum plugin installationCheck your CMS or website's plugin directory for 'Upqode Plum' in the list of installed pluginsAffected if The Upqode Plum plugin is installed on the system
-
Confirm plugin versionAccess the plugin details page in your CMS admin panel or inspect the plugin header comment in the main plugin file to determine the exact version numberAffected if The installed version matches any affected version range provided by the vendor or security advisory
-
Review user role permissionsNavigate to the plugin's settings or admin panel and examine which user roles have access to sensitive features (e.g., content management, configuration options, user management)Affected if Lower-privileged users (like subscribers or contributors) can access functionality typically restricted to administrators
-
Inspect for unauthorized administrative accountsCheck the user management section of your CMS for any newly created accounts with administrator or elevated privileges that you did not createAffected if Unexpected admin accounts exist in the system
-
Scan for suspicious stored contentReview recent posts, pages, comments, or custom content types created by non-admin users for unfamiliar scripts, iframes, or malicious HTML/JavaScript codeAffected if Stored XSS payloads or suspicious scripts are present in user-submitted content that executes when viewed by other users
-
Audit plugin activity logsExamine server access logs or CMS activity logs for requests to plugin endpoints that should require higher privileges, especially from low-privileged user accountsAffected if Requests to sensitive plugin functions originate from users lacking proper authorization
You are affected if the Upqode Plum plugin is installed AND you observe unauthorized access to privileged features by low-privilege users, unexpected admin accounts, or malicious scripts in stored content.
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 to the patched version of the plugin when released; until then, restrict plugin access to trusted administrators only and monitor for suspicious script injection in wheel/popup configurations.
- 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-2024-38744 — 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-2024-38744 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