CVE-2019-25635
Received Received - Intake
Multiple SQL Injection Vulnerabilities in Zeeways Matrimony CMS

Publication date: 2026-03-24

Last updated on: 2026-04-15

Assigner: VulnCheck

Description
Zeeways Matrimony CMS contains multiple SQL injection vulnerabilities that allow unauthenticated attackers to manipulate database queries through the profile_list endpoint. Attackers can inject SQL code via the up_cast, s_mother, and s_religion parameters to extract sensitive database information using time-based or error-based techniques.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-24
Last Modified
2026-04-15
Generated
2026-05-27
AI Q&A
2026-03-24
EPSS Evaluated
2026-05-25
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
zeeways matrimony_cms *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2019-25635 is a set of multiple SQL injection vulnerabilities in the Zeeways Matrimony CMS, specifically in the /profile_list endpoint.

These vulnerabilities allow unauthenticated attackers to inject malicious SQL code through the parameters up_cast, s_mother, and s_religion.

Attackers can exploit these flaws using time-based or error-based SQL injection techniques to manipulate database queries and extract sensitive information.


How can this vulnerability impact me? :

This vulnerability can lead to unauthorized access to sensitive database information by allowing attackers to manipulate SQL queries.

Because the attack requires no authentication and no user interaction, it can be exploited remotely over the network.

The impact includes potential data disclosure (high confidentiality impact) and partial data integrity loss (low integrity impact), but it does not affect availability.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by sending crafted SQL injection payloads to the /profile_list endpoint targeting the parameters up_cast, s_mother, and s_religion. These payloads exploit SQL functions such as row(), concat(), and CHAR() combined with random number generation to trigger database errors or extract data.

Example detection commands include sending POST or GET requests with SQL injection payloads like the following:

  • POST request to /profile_list with parameter up_cast containing a payload using row(1,1), concat(), and CHAR() functions to cause SQL errors.
  • GET request to /profile_list with parameter s_mother containing a URL-encoded SQL injection payload similar to the above.
  • POST request to /profile_list?s_mother=1 with parameter s_religion containing a similar SQL injection payload.

These payloads can be sent using tools like curl or specialized SQL injection testing tools to observe error messages or timing differences indicating vulnerability.


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart