CVE-2025-52794
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 Creative-Solutions Creative Contact Form sexy-contact-form allows Stored XSS.This issue affects Creative Contact Form: from n/a through <= 1.0.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 confidenceCross-Site Request Forgery (CSRF) vulnerability in Creative-Solutions Creative Contact Form (sexy-contact-form) allows attackers to trick authenticated users into submitting requests that inject malicious scripts, leading to Stored XSS that persists on the server and affects other users viewing the compromised content.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Identify if Creative Contact Form is installedLocate the sexy-contact-form plugin or component in your CMS/plugin directory, or check your website's source code for references to 'sexy-contact-form' or 'Creative Contact Form'Affected if The plugin/component is present in the environment
-
Determine the installed versionCheck the plugin's version file, readme.txt, or main PHP file for a version constant; compare against any official release notesAffected if The installed version is unknown or falls within a vulnerable range if one exists
-
Inspect form submissions for anti-CSRF tokensExamine the HTML source of contact forms served by the plugin; look for hidden input fields containing tokens (e.g., name='csrf_token' or similar) or check request headers for token validation in the server-side codeAffected if No anti-CSRF tokens are found in form markup or server-side validation logic
-
Check server-side input sanitizationReview the form handling PHP code for functions that sanitize or validate user inputs (e.g., htmlspecialchars, strip_tags, preg_match for allowed characters); test by submitting HTML/JavaScript in form fieldsAffected if User inputs are not sanitized or validated before being stored in the database
-
Verify output encoding on stored contentReview code that retrieves and displays submitted form data; check if output is encoded (e.g., using htmlspecialchars with ENT_QUOTES) when rendered to other usersAffected if Stored form submissions are rendered without proper encoding, allowing injected scripts to execute
Users are affected if the Creative Contact Form (sexy-contact-form) is installed and lacks anti-CSRF tokens and proper input sanitization/ output encoding, enabling Stored XSS via CSRF.
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 in all form submissions and validate/sanitize all user inputs on the server side while encoding output to prevent XSS execution.
- 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-2025-52794 — 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-2025-52794 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