Having worked in a few large shops, I suspect what you are describing is an internal application (firewalled off), therefore the concern by management about getting cracked is minimal.

If this is a serious application, as opposed to lets say an internal app that collects suggestions for the departments next picnic location, then you should perhaps push your point. Before doing so, make sure you can articulate how this can be a problem (which is one reason you are here now, a good start)...what are the ramifications of having bad data? i.e. Can someone give themselves a raise?, modify their vacation days? put their daily pizza order on the company card? obtain a staple and paperclip supply above and beyond the maximum allowed? If the risk is trivial, and management isn't interested in hearing about good coding practice, then back off and treat this as a learning experience.

If you have a traditional Dev/test/prod type environment, then your risk of demonstrating the flaw is greatly diminished. Since you admit being new to Perl (as well as the company) I would suggest garnering some support from those more experienced, someone who is respected by your management/peers (is there a "guru" around?). Another option depending on the size of the company is to speak directly to a representative of a IT support dept, preferrably security. Explain the scenario and ask for advice. If they are doing their job, they will quite possibly take the ball and just run with it (be sure that your manager knows you are seeking their consultation, so he/she's not blindsided by a overzealous security analyst).

Appears to me like you are simply being a conscientous employee. Hopefully you work in a place where such behavior is valued. good luck.

In reply to Re: The danger of hidden fields by wardk
in thread The danger of hidden fields by Gerard

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.