CspriteWordPress extension · Creatomatic
CVE-2023-49763
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) vulnerability in Creatomatic Ltd CSprite.This issue affects CSprite: from n/a through 1.1.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in Creatomatic Ltd CSprite version 1.1 and earlier. The vulnerability allows remote attackers to perform unauthorized state-changing actions on behalf of authenticated users by tricking them into visiting malicious web pages. With a CVSS score of 8.8 (HIGH), this indicates low attack complexity and significant impact to confidentiality and integrity.
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
CspriteWordPress extension
<= 1.1CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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.
-
Identify CSprite versionLocate the installed CSprite application and check its version information, typically found in the application header, about page, or software metadata file. Compare the version number to the affected range: version 1.1 or earlier.Affected if The installed version is 1.1 or any earlier version number.
-
Inspect state-changing forms for anti-CSRF tokensExamine the HTML source code of forms that perform state-changing actions (such as user settings modifications, data submissions, or authentication-related operations). Look for hidden input fields containing unique tokens or checks for existing token validation in the server-side processing logic.Affected if State-changing forms lack anti-CSRF token fields and the server does not validate tokens on form submissions.
-
Verify SameSite cookie attributesInspect the authentication and session cookies set by CSprite using browser developer tools or by intercepting HTTP responses. Check if the Set-Cookie headers include the SameSite attribute with a value of Strict or Lax.Affected if Cookies are set without the SameSite attribute or have SameSite=None without Secure, indicating insufficient CSRF protection.
-
Check Origin and Referer header validationReview the server-side code or configuration that handles form submissions to determine if the application validates the Origin or Referer HTTP headers before processing state-changing requests.Affected if The application does not validate Origin or Referer headers on state-changing operations, allowing requests from arbitrary origins.
A user is affected if they run CSprite version 1.1 or earlier AND the application lacks anti-CSRF tokens on state-changing operations, proper SameSite cookie attributes, and Origin/Referer header validation.
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 anti-CSRF tokens on all state-changing operations, configure SameSite cookies, and validate Origin/Referer headers to prevent CSRF attacks. Additionally, consider implementing SameSite=Strict or SameSite=Lax attributes for authentication cookies.
Fix this in Csprite
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.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 $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49763 — 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-49763 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