MYTH: I'm not allowed to install modules
The Basics
Generally this is not the case, modules are generally just text files.
You just put these text files on your system, and then tell Perl how to find them.
If you have a system where you are not allowed to write text-files, period, then you are not programming anything.
If management decree that you are not allowed 3rd party code of any form, then you may have an argument, and possibly poor management.
For the cases where the modules require Binary components built that's quite understandable, but there are generally good alternatives in Pure Perl.
The Alternatives
This is a wonderful guide on how you can set up locally visible modules in Perl without requiring any form of root account.
For the most trivial of modules, you can install only the very basic parts you need by hand.
cd /project
mkdir lib
cd lib
# Say the 'package' in the file is "Foo::Bar::Baz"
mkdir -p Foo/Bar
cd Foo/Bar
wget $url -O Baz.pm
cd /project
And there you have it, you've installed a module into the lib directory of whatever project needs it. Its admittedly a bit messy to do it that way, but it works.
All thats needed is to do in your code:
#!/usr/bin/perl
# /project/foo.pl
#
use strict;
use warnings;
use lib 'lib';
use Foo::Bar::Baz; # Works!
And it should be smooth from there.
Not Using CPAN is a Bad Idea Indeed
Perl modules uploaded to CPAN generally have an entire fleet of testers on different operating systems building them, and running their tests, as well as committing bug reports and contributions for weird edge cases.
The only time you should NOT use an existing module, is when you KNOW as a matter of FACT you can do a better job.
In such cases, its recommended to write your own module, and upload it to CPAN, so that you can benefit from the team of testers who will run it, find bugs, and report them.
If you're really lucky, they'll report bugs with working patches.