CVE-2022-25355
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 · uneditedEC-CUBE 3.0.0 to 3.0.18-p3 and EC-CUBE 4.0.0 to 4.1.1 improperly handle HTTP Host header values, which may lead a remote unauthenticated attacker to direct the vulnerable version of EC-CUBE to send an Email with some forged reissue-password URL to EC-CUBE users.
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 confidenceEC-CUBE fails to validate the HTTP Host header when generating password reissue (reset) URLs in emails. An unauthenticated remote attacker can manipulate the Host header to cause the application to generate password reset emails containing attacker-controlled URLs, potentially allowing credential theft via phishing.
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>= 3.0.0, < 3.0.18>= 4.0.0, <= 4.1.1= 3.0.18CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Identify installed EC-CUBE versionLocate the version file or check the administration panel for the installed EC-CUBE version numberAffected if Version is >= 3.0.0 and < 3.0.18, OR = 3.0.18, OR >= 4.0.0 and <= 4.1.1
-
Confirm password reset functionality is in useVerify that the site has user registration enabled and password reset/reset functionality is accessibleAffected if Password reset feature is active and users can request password reset emails
-
Check for Host header validation in application configurationReview the application configuration files and codebase for any whitelist or validation logic that restricts allowed Host header valuesAffected if No Host header validation whitelist is configured or implemented
-
Inspect password reset email templatesExamine the password reset email template code to determine if the reset URL is constructed using the HTTP Host header value directlyAffected if The reset URL is built using the incoming Host header without validation
Your environment is affected if you are running a vulnerable EC-CUBE version AND the password reset URL generation relies on the unvalidated Host header.
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 · scoped3.0.18
Implement strict Host header validation using an allowlist of permitted domain names, and/or use relative URLs with server-configured base URLs instead of relying on the Host header for constructing email links.
EC-CUBE 3.0.18-p3 or later for 3.x line; EC-CUBE 4.1.2 or later for 4.x line
- 1. Identify the current EC-CUBE version by checking the version file or admin panel
- 2. For EC-CUBE 3.x versions (3.0.0 to 3.0.18-p3): Upgrade to version 3.0.18-p3 or later
- 3. For EC-CUBE 4.x versions (4.0.0 to 4.1.1): Upgrade to version 4.1.2 or later
- 4. Before upgrading, backup the database and all files
- 5. Review the official EC-CUBE upgrade documentation for your specific version path
- 6. Perform the upgrade in a staging environment first to verify compatibility
- 7. After upgrade, verify that the HTTP Host header is properly validated and the password reissue emails contain correct URLs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25355 — 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-2022-25355 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