AFAIK, not really since the system does clear the HW flags (and introduces ~1µs+ latency) prior calling your handler .
The easiest way would be to donate one ISR per pin to register which pin actually fired and from that ISR you can call a generic function that does the common jobs.
Or, sample the pins (using pinReadFast() for example) to see which one changed, causing the interrupt. This will require that you maintain the previous pin states.