CVE-2025-0744
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 · uneditedan Improper Access Control vulnerability has been found in EmbedAI 2.1 and below. This vulnerability allows an authenticated attacker change his subscription plan without paying by making a POST request changing the parameters of the "/demos/embedai/pmt_cash_on_delivery/pay" endpoint.
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 confidenceAn Improper Access Control vulnerability in EmbedAI 2.1 and below allows authenticated users to manipulate subscription plan pricing during checkout by modifying POST parameters to the /demos/embedai/pmt_cash_on_delivery/pay endpoint, bypassing proper payment validation and authorization checks.
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< 2.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 EmbedAI versionLocate the version file or header in the Thesamur EmbedAI installation directory. Common locations include a version.php file, composer.json, or the admin dashboard about page. Compare the version number to the affected range: versions below 2.1 are vulnerable.Affected if The installed version is Thesamur EmbedAI version 2.1 or below.
-
Verify the vulnerable payment endpoint existsCheck if the file path /demos/embedai/pmt_cash_on_delivery/pay exists in the web root. This endpoint handles cash on delivery payment processing and is the entry point for the vulnerability.Affected if The /demos/embedai/pmt_cash_on_delivery/pay endpoint file exists and is accessible via HTTP.
-
Confirm the cash on delivery payment module is enabledInspect the application configuration or module settings to determine if the pmt_cash_on_delivery payment module is active. Check for related configuration files in the modules or config directory.Affected if The cash on delivery payment module (pmt_cash_on_delivery) is enabled in the system.
-
Check user authentication is activeVerify that user authentication and subscription functionality are enabled. The vulnerability requires an authenticated user session to exploit the price manipulation during checkout.Affected if User registration and authentication are enabled, allowing users to access subscription checkout flows.
A system is affected if it runs Thesamur EmbedAI version 2.1 or below with the cash on delivery payment module enabled and accessible to authenticated users via the /demos/embedai/pmt_cash_on_delivery/pay endpoint.
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 data2.1
Implement server-side validation of payment amounts and subscription pricing, verify payment status against a trusted payment gateway before granting access, and enforce proper authorization checks to ensure users can only access subscription plans they have paid for.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0744 — 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-0744 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