Where the password is passed from the dbpro exe to the plugin is another potential problem.
It's not difficult to swap a dll in a dbpro exe with another one. The replacement dll could pop up a message box showing the password instead of using it to connect to a database.
I'd also be a little concerned how query strings where handled.
If you did something like this to check a username + password before loggin a user on.
+ Code Snippetq$ = "select * from users where name = " + name$ + " and pass = " + pass$ + ";"
Someone may be able to open the exe in a hex editor, find those strings and change the values to alter the query.
If you found and altered
" and pass = "
to
";--d pass = "
You would end up with
select * from users where name = 'someuser';--d pass = 'somepass';
Now the user gets logged in without needing a correct password.
Probably very few people would know how and have the inclination to do either but it's what they could do if they did that would worry me. Getting the password would allow them to connect with another password and do whatever the user had knowledges to do. That would presumably include reading and manipulating others data.