CVE-2025-47289
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 · uneditedCE Phoenix is a free, open-source eCommerce platform. A stored cross-site scripting (XSS) vulnerability was discovered in CE Phoenix versions 1.0.9.9 through 1.1.0.2 where an attacker can inject malicious JavaScript into the testimonial description field. Once submitted, if the shop owner (admin) approves the testimonial, the script executes in the context of any user visiting the testimonial page. Because the session cookies are not marked with the `HttpOnly` flag, they can be exfiltrated by the attacker — potentially leading to account takeover. Version 1.1.0.3 fixes the issue.
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 confidenceStored XSS in CE Phoenix testimonial description field (v1.0.9.9-1.1.0.2) allows attackers to inject malicious JavaScript that executes when users view admin-approved testimonials. Combined with missing HttpOnly flag on session cookies, attackers can exfiltrate session credentials for account takeover.
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< 1.1.0.3CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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 installed Phoenix Cart versionLocate the version file or admin panel version display. Common locations include the root version.php file, admin/version.php, or the admin dashboard footer which typically shows the version number. Compare the installed version to the affected range (1.0.9.9 through 1.1.0.2) or any version below 1.1.0.3.Affected if The installed version is 1.0.9.9, 1.1.0.0, 1.1.0.1, 1.1.0.2, or any version lower than 1.1.0.3
-
Verify testimonial module is accessibleCheck if the testimonials feature is enabled in the admin panel under Modules or Content Manager, or attempt to access the testimonials page on the storefront (typically /testimonials.php). Confirm that the installation has testimonials functionality present and active.Affected if The testimonials module is installed and enabled, allowing user-submitted testimonials to be created and viewed
-
Inspect session cookie HttpOnly flag configurationUse browser developer tools (Application tab > Cookies) or a proxy to capture a login request to the site. Examine the Set-Cookie headers for session-related cookies (typically osCsid, PHPSESSID, or similar session identifiers) and verify whether the HttpOnly attribute is present.Affected if Session cookies are missing the HttpOnly flag, allowing JavaScript access to session identifiers
-
Check testimonial submission form existenceNavigate to the storefront testimonials page or locate the testimonial submission form in the code. Identify if there is a description or message input field where users can enter custom content.Affected if A testimonial submission form with a description field exists and accepts user input
-
Review admin-approved testimonial display flowAccess the testimonials page on the storefront as a logged-in user. Submit a test testimonial with admin approval enabled (if configurable), then verify whether submitted testimonials are displayed to other users after admin approval.Affected if Testimonials require admin approval before display, meaning the stored XSS would trigger when approved testimonials are viewed by users
You are affected if running Phoenix Cart version 1.0.9.9 through 1.1.0.2 with the testimonials module enabled, and session cookies lack the HttpOnly flag, allowing stored XSS in testimonials to steal session credentials.
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.
dbcve · scoped1.1.0.3
Immediately upgrade to version 1.1.0.3 and configure all session cookies with the HttpOnly flag to prevent client-side script access.
1.1.0.3
- 1. Create a complete backup of the current CE Phoenix Cart installation including database and files
- 2. Download CE Phoenix Cart version 1.1.0.3 from the official repository (github.com)
- 3. Extract the upgrade package and upload all files to the server, overwriting existing files
- 4. Run any database migration scripts included in the upgrade if applicable
- 5. Clear all cached files and sessions
- 6. Verify the upgrade was successful by logging into the admin panel
- 7. Confirm the testimonial module now properly sanitizes input and/or implements HttpOnly flags on session cookies
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2025-47289 — 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-47289 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