CVE-2025-13121
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 · uneditedA security vulnerability has been detected in cameasy Liketea 1.0.0. Impacted is the function list of the file laravel/app/Http/Controllers/Front/StoreController.php of the component API Endpoint. Such manipulation of the argument lng/lat leads to sql injection. The attack may be performed from remote. The exploit has been disclosed publicly and may be used.
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 confidenceSQL injection vulnerability in cameasy Liketea 1.0.0's StoreController.php API endpoint allows remote attackers to inject malicious SQL queries via the lng/lat parameters. The vulnerability stems from unsanitized user input being directly used in database queries.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 cameasy Liketea is installedLocate the application installation directory and check for StoreController.php in the controllers path, or look for Liketea branding/version filesAffected if The application is present and uses the Liketea codebase version 1.0.0
-
Verify the vulnerable StoreController.php existsSearch for StoreController.php and inspect it for direct usage of lng/lat parameters in SQL queries without parameterizationAffected if StoreController.php contains unsanitized lng/lat parameters used in database queries
-
Confirm the API endpoint is accessibleTest access to the StoreController API endpoint that accepts lng/lat parameters (typically /api/store or similar path)Affected if The API endpoint accepting lng/lat input is publicly or internally accessible
-
Check for parameterized query implementationReview the StoreController.php code to determine if database queries use prepared statements, parameterized queries, or Laravel's Eloquent ORM with bound parametersAffected if Queries do not use parameterized queries or Eloquent with input binding (direct $_GET or request()->input() in SQL strings)
-
Determine database user privilegesReview the database configuration to identify what privileges the application database user hasAffected if The application database user has permissions beyond read-only (allows INSERT/UPDATE/DELETE)
If cameasy Liketea version 1.0.0 is running with the StoreController.php API endpoint accessible and the lng/lat parameters are used directly in SQL without parameterization, the environment is affected by CVE-2025-13121.
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 dataReplace direct parameter usage in SQL queries with parameterized queries or Laravel's Eloquent ORM methods with proper input validation to prevent SQL injection attacks.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13121 — 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-13121 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