Bug 21051 - CGI::param called in list context when editing a patron card layout
Summary: CGI::param called in list context when editing a patron card layout
Status: RESOLVED DUPLICATE of bug 18320
Alias: None
Product: Koha
Classification: Unclassified
Component: Label/patron card printing (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal (vote)
Assignee: Chris Nighswonger
QA Contact: Testopia
URL:
Keywords:
Depends on: 16154
Blocks: 29771
  Show dependency treegraph
 
Reported: 2018-07-08 14:57 UTC by Katrin Fischer
Modified: 2022-01-10 13:40 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Katrin Fischer 2018-07-08 14:57:46 UTC
To test:
- Edit a patron card layout
- Save or cancel editing


CGI::param called in list context from package CGI::Compile::ROOT::home_vagrant_kohaclone_patroncards_edit_2dlayout_2epl line 186, this can lead to vulnerabilities. See the warning in "Fetching the value or values of a single named parameter" at /usr/share/perl5/CGI.pm line 436.
CGI::param called in list context from package CGI::Compile::ROOT::home_vagrant_kohaclone_patroncards_edit_2dlayout_2epl line 186, this can lead to vulnerabilities. See the warning in "Fetching the value or values of a single named parameter" at /usr/share/perl5/CGI.pm line 436.
CGI::param called in list context from package CGI::Compile::ROOT::home_vagrant_kohaclone_patroncards_edit_2dlayout_2epl line 186, this can lead to vulnerabilities. See the warning in "Fetching the value or values of a single named parameter" at /usr/share/perl5/CGI.pm line 436.
CGI::param called in list context from package Template::Document line 57, this can lead to vulnerabilities. See the warning in "Fetching the value or values of a single named parameter" at /usr/share/perl5/CGI.pm line 436.
Comment 1 Jonathan Druart 2022-01-10 13:40:40 UTC

*** This bug has been marked as a duplicate of bug 18320 ***