This is the key point. Yes refactoring is not a bad idea but have you spent enough time with the current codebase to understand why things are done the way they are ? Even if the code is sphagetti, the point is that you may not have all the background yet on things and you need to spend a bit more time understanding everything before you suggest major refactoring. Not to mention that unless it helps with real dollars (more money for the team/company), you may face resistance.
Having said that, don't be afraid to challenge status quo but make sure you have enough background information before making assumptions. It is much easier to come from outside and look at everything being broken (which may very well be but still need to understand it in detail).